Converting Physical Citrix Server to VMware Using VMware Converter

We converted one of our physical Citrix servers yesterday to VMware ESXi also and it went smoothly as well.  No issues so far, so if you’re thinking of doing the same thing I can confirm that it works.

We also use RSA SecurID for authentication and it still works after the conversion with no changes made to the RSA Authentication Manager or RSA ACE Agent (using the same IP address after the conversion of course).

More P2V conversions next week .

Converting Microsoft Virtual Server 2005 Virtual Machines to VMware

We just converted 3 of our virtual machines running on Virtual  Server 2005 R2 to VMware ESXi yesterday and it went pretty smoothly with just a couple of minor issues.

The first issue is the mouse cursor not working in VMware console after installing the VMware tools.  The fix is just a simple registry edit:

1. Open Registry Editor (regedit)
2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\{4D36E96F-E325-11CE-BFC1-08002BE10318}
3. Double-click on UpperFilters and delete msvmmouf.
4. Reboot the VM.

Source: http://www.petri.co.il/forums/archive/index.php/t-19387.html

The second minor issue is when you try to set the static IP address to the same IP address before it was converted, you might receive a message similar to this:

The IP address XXX.XXX.XXX.XXX you have entered for this network adapter is already assigned to another adapter Name of adapter. Name of adapter is hidden from the network and Dial-up Connections folder because it is not physically in the computer or is a legacy adapter that is not working. If the same address is assigned to both adapters and they become active, only one of them will use this address. This may result in incorrect system configuration. Do you want to enter a different IP address for this adapter in the list of IP addresses in the advanced dialog box?

This is probably not a big deal, but if it bothers you just do the following:

1. Click Start, click Run, type cmd.exe, and then press ENTER.
2. Type set devmgr_show_nonpresent_devices=1, and then press ENTER.
3. Type Start DEVMGMT.MSC, and then press ENTER.
4. Click View, and then click Show Hidden Devices.
5. Expand the Network Adapters tree.
6. Right-click the dimmed network adapter, and then click Uninstall.

Source: http://support.microsoft.com/kb/269155

How to query Active Directory using SQL Server

Here is one of those things that I wish I had known much sooner.  Very useful and a big time saver.  I just found out about this a few months ago when I wanted to run a report against AD to see if the account info are consistent and up to date, to see which accounts have passwords set to never expire, when they were created/last updated, etc.

So I asked myself whether it’s possible to query AD directly from SQL.  The first thing I did was do a search on Google of course and sure enough I found this website with instructions on how to do it!

Here are the steps:

1. Create a linked server to AD using this command in Query Analyzer:

sp_addlinkedserver ‘ADSI’, ‘Active Directory Service Interfaces’, ‘ADSDSOObject’, ‘adsdatasource’

2. Create views using the example below, I’m calling them vADUsers and vADGroups (replace calazan and com with your domain, add more AD attributes to the view as needed):

CREATE VIEW vADUsers AS
SELECT *
FROM OPENQUERY (ADSI,
‘SELECT co, whenCreated, whenChanged, sAMAccountName, sn, givenName, displayName, mail, telephoneNumber, mobile,
physicalDeliveryOfficeName, facsimileTelephoneNumber, title, department, company, manager, ipPhone, userAccountControl, badPwdCount
FROM ”LDAP://DC=calazan,DC=com”
WHERE objectCategory = ”Person” AND objectClass = ”user”’)

CREATE VIEW vADGroups AS
SELECT *
FROM OPENQUERY (ADSI,
‘SELECT displayName, groupType, mail, name, info, whenChanged, whenCreated
FROM ”LDAP://DC=calazan,DC=com”
WHERE objectClass = ”group”’)

3. Query the views just like you’re querying a normal SQL table:

I also recommend that you download the free ADSI Edit tool (adsiedit.msc) to see all the attributes available in your Active Directory site.  Microsoft Office Communications Server 2007 and Exchange Server 2007 for example extend the AD schema and you might want to query some of those extra attributes as well.

Exchange 2007 SP1: Message rejected as spam by Content Filtering

Error Message: “550 5.7.1 Message rejected as spam by Content Filtering.”

One of our users reported that after we applied Service Pack 1 and Update Rollup 1 to Exchange Server 2007, some of the emails that he has scheduled to send daily were getting rejected with the message above.

I guess the integrated anti-spam in Exchange got updated as well.

You can configure Content Filtering in Exchange to bypass specific users or domains.

Open the Exchange Management Shell:

# To check the Content Filter configuration, type in:

Get-ContentFilterConfig

# To set the Bypassed Senders (example):

Set-ContentFilterConfig -BypassedSenders donotspamme@calazan.com, jdoe@abc.com

# To set the Bypassed Sender Domains (example):

Set-ContentFilterConfig -BypassedSenderDomains calazan.com, *.xyz.com

Important Note: BypassedSenders and BypassedSenderDomains are multivalued properties. When you use the Set-ContentFilterConfig cmdlet, it will overwrite the values of those properties. If you just need to add more senders or domains, please follow the example below.

# To add Bypassed Senders:

$x = Get-ContentFilterConfig

$x.BypassedSenders += “jsmith@google.com”, “bhope@yahoo.com”

# To remove Bypassed Senders (can only be done one at a time):

$x = Get-ContentFilterConfig

$x.BypassedSenders -= “jsmith@google.com”

# To empty the list:

Set-ContentFilterConfig -BypassedSenders $null

Exchange Management Tools SP1: Service Remote Registry failed to reach status “Stopped”

I got this error while upgrading the Exchange Management Tools on my Windows XP computer at work to Service Pack 1. I checked the services and the Remote Registry service is stuck at “Stopping” status.

To fix this, simply set the Remote Registry service’s startup type to Manual, reboot your computer, try installing Exchange Server 2007 SP1 Management Tools again and it should now install successfully. The Remote Registry service will automatically start and the startup type will go back to Automatic after the installation.

Upgrading to Exchange Server 2007 SP1

We just upgraded from Exchange 2007 RTM to Exchange 2007 SP1 yesterday morning and I’m happy to say that the upgrade went very smoothly. It took about 20 minutes.

Here are some things to consider:

1. Install .NET Framework 2.0 SP1 before upgrading. This may not be required but Microsoft recommends it.
2. If you have more than one Exchange server, Microsoft recommends that you upgrade the servers running the Mailbox server role last. Upgrade your servers in the following order:
   1. Client Access servers
   2. Unified Messaging servers
   3. Hub Transport servers
   4. Edge Transport servers
   5. Mailbox servers
3. If you have third party software running on the Exchange server, stop the services/processes for those software before running the SP1 installation (e.g. antivirus, Backup Exec Remote Agent, etc.).
4. Check the compatibility of other software that use/connect to the Exchange server. Some examples:
   1. BlackBerry Enterprise Server. We have BES version 4.1.3 and I can confirm that this version works with Exchange 2007 SP1. E-mails, contacts, calendar, tasks, notes, Out-of-Office are synchronizing properly. No issues so far. I’m assuming that higher versions would also work.
   2. Symantec Backup Exec 11d. Make sure that you upgrade the Exchange Management Tools on the server running Backup Exec to Service Pack 1 as well (and install other patches for Exchange that you have installed on your Exchange server) or you may get this error: Unable to complete the operation for the selected resource using the specified options. The following error was returned when opening the Exchange Database file: ‘-514 The version of the log file is not compatible with the ESE version.’ Go here for more details: http://seer.entsupport.symantec.com/docs/289970.htm.

5. Read the release notes.

Update Rollup 1 for Exchange Server 2007 Service Pack 1 (KB945684) was also just released three days ago and you may want to install this as well.

WMI: Access is denied. (Exception from HRESULT: 0×80070005)

We have one computer at work that I couldn’t send a Remote Assistance request to and whenever I try to query it using WMI and PowerShell I get the following error message:

Get-WmiObject : Access is denied. (Exception from HRESULT: 0×80070005 (E_ACCESSDENIED))

The problem turned out to be DCOM. For some reason it got disabled.

To change its settings, do the following:

1. Go to Start -> Run, type in dcomcnfg.
2. Go to Component Services -> Computers.
3. Right-click on My Computer and select Properties.
4. Go to the Default Properties tab.
5. Make sure that Enable Distributed COM on this computer is checked.
6. Compare the settings to a computer that is working properly and make the necessary changes. Compare the settings for the COM Security tab as well.
7. Reboot the computer and try it again.

Credit goes to this website where I found this solution.

How to enable Remote Desktop remotely

I had to do this just a few minutes ago and I figured I should probably post it here.

1. Open Registry Editor by going to Start -> Run and typing in regedit.
2. Go to File -> Connect Network Registry… and type in the name of the computer where you want Remote Desktop enabled.  Click OK.
3. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server of that computer.
4. Double-click the DWORD called fDenyTSConnections and set its value to 0.  Click OK.

That’s it! Remote Desktop is now enabled!