[Shoretel] Get list of user extension, login, workgroup description with firstname & last name based on the Workgroup number.

Below is the SQL where to get a list of user extension, login, workgroup description with firstname & last name based on the Workgroup numbeer where 1234, 2456 are workgroup extension numbers.

SELECT workgroupmembers.WorkgroupDN,workgroupmembers.UserDN,users.GuiLoginName,tabaddresses.FirstName,tabaddresses.LastName,dn.Description FROM workgroupmembers

INNER JOIN `dn` ON workgroupmembers.WorkgroupDN=dn.DN

INNER JOIN `users` ON workgroupmembers.UserDN=users.UserDN

INNER JOIN `tabaddresses` ON users.AddressID=tabaddresses.AddressID

WHERE workgroupmembers .WorkgroupDN IN (1234, 2456)

ORDER BY workgroupmembers.WorkgroupDN ASC
Advertisements

[SHORETEL] Extract user’s corresponding workgroups

Below is the SQL for Shoretel to user’s corresponding workgroups where 1234 is the user’s extension.

SELECT workgroupmembers.WorkgroupDN,workgroupmembers.UserDN,users.GuiLoginName, tabaddresses.FirstName,tabaddresses.LastName,dn.Description FROM workgroupmembers

INNER JOIN `dn` ON workgroupmembers.WorkgroupDN=dn.DN

INNER JOIN `users` ON workgroupmembers.UserDN=users.UserDN

INNER JOIN `tabaddresses` ON users.AddressID=tabaddresses.AddressID

WHERE users.UserDN IN (1234)

[KACE] Dell BIOS Admin Password Status Custom Inventory Field

To add a Custom Inventory Field (CIF) in Kace for Dell BIOS admin password status, use the below Custom Inventory Rule (CIR)

This CIF assumes that you have Dell Command | Monitor installed.

ShellCommandTextReturn(c:\windows\sysnative\WindowsPowerShell\v1.0\powershell.exe "invoke-command -ScriptBlock {Get-WmiObject -namespace "root\DCIM\SYSMAN" -Class DCIM_BIOSPassword| where-object {$_.AttributeName -eq 'AdminPwd'}|Select -ExpandProperty IsSet} -ErrorAction SilentlyContinue" 2> nul)

 

 

[KACE] Hard Disk Failure Prediction Custom Inventory Field

To add a Custom Inventory Field (CIF) in Kace for hard disk failure prediction, use the below Custom Inventory Rule (CIR)

ShellCommandTextReturn(powershell.exe "invoke-command -ScriptBlock {Get-WmiObject -Namespace root\wmi -Class MSStorageDriver_FailurePredictStatus|Select-Object -ExpandProperty PredictFailure -First 1} -ErrorAction SilentlyContinue" 2> nul)

 

This CIR will retrieve the first record returned by the command, which in most case, is the system disk.

 

[KACE] Symantec Endpoint Protection SyLink Custom Inventory Field

To add a Custom Inventory Field (CIF) in Kace for Symantec Endpoint Protection SyLink, use the below Custom Inventory Rule (CIR)

ShellCommandTextReturn(powershell.exe "invoke-command -ScriptBlock {write-host ([xml](Get-Content -Path 'C:\ProgramData\Symantec\Symantec Endpoint Protection\CurrentVersion\Data\Config\syLink.xml')).SelectSingleNode('//Server[1]').address} -ErrorAction SilentlyContinue" 2> nul)

 

This CIR will read the XML for the server SEP is communicating with.

 

[KACE] Symantec Desktop Encryption Status Custom Inventory Field

To add a Custom Inventory Field (CIF) in Kace for the encryption status of Symantec Desktop Encryption, use the below Custom Inventory Rule (CIR)

ShellCommandTextReturn("C:\Program Files (x86)\PGP Corporation\PGP Desktop\pgpwde.exe" --status)

 

Details of the command and reference can be found at :

https://support.symantec.com/en_US/article.TECH204285.html

 

Downloading Dell Driver CAB files automagically with the Driver Pack Catalog

Another piece of puzzle solved for Dell drivers management

deploymentramblings

Dell has been hard at work behind the scenes trying to make our lives as IT Pros easier.  From their Enterprise Client Tools such as OMCI and the Client Configuration Toolkit (CCTK) to the more recent (past few years) Driver CAB files.  Well yesterday we got another tool to help us in the fight to manage our drivers and ease the pain of obtaining them.  Yesterday Dell unleashed the Dell Driver Pack Catalog.

What is the Dell Driver Pack Catalog you ask?  Warren Byle (Dell) sums it up nicely:

                The Driver Pack Catalog is an XML file containing metadata about the  new Dell systems and WinPE Driver Packs. This XML file is compressed as a Microsoft Cabinet (.CAB) file and digitally signed for delivering it to the customers over the internet.

Basically, it gives is a structured way of identifying the latest and greatest driver packages (CABs) available from…

View original post 263 more words

[PowerShell] Making good use of AD Computer object ManagedBy field

If you put the assignee of the computer in the computer object’s ManagedBy field, you will be able to search for it based on the username of the assignee with the following script

$username = Read-Host 'Please enter Username'
$userDistinguishedName = Get-ADUser -Filter "SamAccountName -eq '$username'"|Select-Object -ExcludeProperty DistinguishedName
Get-ADComputer -Filter "ManagedBy -eq '$($userDistinguishedName)'" -Properties IPv4Address,OperatingSystem,OperatingSystemServicePack,OperatingSystemHotfix,Description|Select-Object Name,IPv4Address,OperatingSystem,OperatingSystemServicePack,OperatingSystemHotfix,Description|ft -AutoSize

[PowerShell] Getting a list of users that has full-access rights to a mailbox

Below is the PowerShell Cmdlet that lets you get a list of members that has FullAccess right to a mailbox.

Get-MailboxPermission -Identity mailbox|select Identity, User,AccessRights|where{$_.AccessRights -match "FullAccess"}

To have the result on your clipboard, add |clip to the end of the command as below

Get-MailboxPermission -Identity mailbox|select Identity, User,AccessRights|where{$_.AccessRights -match "FullAccess"}|clip

Improve autodiscover performance

Nice to know the steps about auto discovery

Jaap Wesselius

Autodiscover can be a lengthy process, especially if you are in a hosted environment or if your mailbox is in Office 365.

The autodiscover process consists of five different steps, it depends on your environment where autodiscover stops and returns the information. Autodiscover is using the following mechanisms:

  • Service Connection Point (SCP) in Active Directory. This is used by domain clients.
  • Root domain discovery, used by non domain joined clients or clients not being able to access Active Directory. All other steps are used by these clients as well.
  • Autodiscover.contoso.com (standard autodiscover mechanism)
  • Autodiscover redirect to autodiscover site (often used by hosting companies)
  • Autodiscover SRV records in DNS (sometimes used by hosting companies)
  • Autodiscover redirect to Office 365 (outlook.com)

If your mailbox is in Office 365, outlook will go through all these steps until it finds the information in Office 365. All steps will fail with the accompanying time-out and…

View original post 186 more words