Finding Windows Server Versions and Editions in Active Directory

I came across this requirement at one of my customer’s environment. They have a huge network of Windows Server systems and do not have any details of their Windows Servers in Active Directory. Unfortunately, Active Directory stores very limited information with Computer accounts so it becomes necessary to logon to each computer and then find out this information. In our case we had more than 350 servers which made it even more difficult. Computers running Windows Vista and later and Windows 2008 and later will add their server edition details with their computer accounts in active directory as well but for the operating systems earlier to Windows 2003 and XP it becomes a trouble.

I prefer using Quest AD cmdlets while working with AD objects because they save a lot of time and lines of code. I have used it one more time here and here is the script that worked for us:

 

$objComputers = Get-QADComputer -SizeLimit 0 -IncludeAllProperties | Where-Object {$_.OperatingSystem -like "Windows Server *"} | Select-Object dnshostName

foreach ($objComputer in $objComputers)

{
    if (Test-Connection -ComputerName $objComputer.dNSHostName -Count 1 -ErrorAction SilentlyContinue)
    {
    $WMIResult = Get-WmiObject Win32_OperatingSystem -ComputerName $objComputer.dNSHostName -ErrorAction SilentlyContinue
    Write-Host $objComputer.dNSHostName ":" $WMIResult.Caption
    }
   
    else
    {
    Write-Host $objComputer.dnsHostname "is not reachable"
    }
}

Here is the output of the script:

image

Please note: you need Quest Active Directory Management Cmdlets installed on the computer where you run this script from.

Changing SIP address of OCS Enabled Users – What is the impact?

I was talking to one of my very good friends yesterday. He was asked to test the impact of changing SIP of the OCS enabled user accounts.

Honestly, its really tricky to answer a question when someone asks you about the predicted impact of changing SIP addresses. I was able to find something related to this here http://blog.insideocs.com/2009/12/17/impact-of-changing-a-users-sip-address/

The article linked above though said that Curtis (the blog author) did not test it change of SIP address in Group Chat.

 

I thought I could check some possibilities in my lab. The results from my lab are something like this.

  • Internal users to your SIP pool or for that matter entire organization will not be affected due to change in their SIP address.
  • The only adverse effect of changing SIP address is the dependant applications in the organization. If you have any application that uses the SIP address for sending IMs to the recipients then these applications would fail. I have a SCOM server in my environment which had a IM channel configured. The SCOM stopped sending emails after I changed SIP address of the user account which was a recipient for SCOM alerts on IM.
  • If you are federated with other organizations and you are also added as a contact in contact list of federated users then your presence to your contacts will not work.
  • Group chat will have no negative effects of changing the SIP address. (I didn’t observe any).
  • Outlook integration of MOC breaks if the SIP address is different than the primary SMTP address of the user mailbox on Exchange server.

As mentioned in the linked blog as well, OCS would generate a UID for each enabled user and it will be stored in the configuration database. Communicator uses this UID for conversation with other OCS enabled users. This is the key point here which keeps the functionality working even after there is a change in SIP addresses.

I would appreciate your comments on this post as there may be several things that I was not able to test.