[stub] The Office Communicator 2007 OCS client requires that the domain name of the FQDN returned for the SRV record _sipinternaltls._tcp.<SIP domain> match the SIP domain. If not, you will not be able to use automatic sign-in.
Monthly Archives: April 2008
DCPROMO install problem
Trying to install a new child domain in an existing forest I received this error from DCPROMO:
—————————
Active Directory Installation Wizard
—————————
The wizard cannot gain access to the list of domains in the forest.
Active Directory Installation Wizard
—————————
The wizard cannot gain access to the list of domains in the forest.
This condition may be caused by a DNS lookup problem. For information about troubleshooting common DNS lookup problems, please see the following Microsoft Web site: http://go.microsoft.com/fwlink/?LinkId=5171
The error is:
The RPC server is unavailable.
A trace of the network traffic during the dcpromo process revealed a connection attempt from the local computer to one of the DCs in the root domain using the computername and username of the local computer. This of course fails since the local computer is to become the first domain controller in the new child domain and thus is in a workgroup. I could not see exactly what the local server was trying to connect to, so I started authenticating to the most common ones: IPC$, C$ and ADMIN$. Turns out it was ADMIN$ and after I ran this command, I was able to continue the dcpromo process:
net use \<name of DC in root domain>admin$ /user:<root domain><administrator in root domain>
Just as dcpromo was starting (after the summary screen) I received another error:
Managing the network session with \<name of DC in root domain> failed
“Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.”
Dcpromo failed after this.
I restarted dcpromo and ran it all the way up to the summary screen. Before I hit Finish I ran this command to delete all connections to remote servers:
net use * /delete
Dcpromo could now successfully complete.
The Dcpromo log was also valuable in troubleshooting this, it can be found in %systemroot%debug.
How to remove the VMWare tray icon for all users
Find this key:
HKEY_LOCAL_MACHINESOFTWAREVMware, Inc.VMware Tools
or, if you’re on x64:
HKEY_LOCAL_MACHINESOFTWAREWow6432NodeVMware, Inc.VMware Tools
Change the ShowTray DWORD value to 0.
Since this is in the HKLM hive it will take precedence over the same setting under HKCU.
If you want to disable the icon only for the logged on user, change the same value but now under HKCU.
How to successfully run Oracle client software on Terminal Server
[stub] Oracle client requires the Create Global Objects user right. Add the required users to the Local Security Policy or a GPO to assign them this right.
How to install Windows Live programs on an unsupported OS
For some reason Microsoft has decided to not let us install any of the Windows Live programs; Messenger, Gallery etc. on Windows Servers or x64 editions of Windows XP. If you try to run the installer (WLInstaller.exe) on any of these OSs you see this error:
—————————
Windows Live Installer
—————————
Sorry, Windows Live programs cannot be installed on Windows Server, Windows XP Professional x64 Edition, or Windows operating systems earlier than Windows XP Service Pack 2.
—————————
OK
—————————
Windows Live Installer
—————————
Sorry, Windows Live programs cannot be installed on Windows Server, Windows XP Professional x64 Edition, or Windows operating systems earlier than Windows XP Service Pack 2.
—————————
OK
—————————
This is quite a problem for Terminal Server users.
To work around this do the following:
- Download and run the WLInstaller.exe on a supported OS.
- Select the programs you want and let the installer finish.
- Navigate to C:Program FilesCommon FilesWindowsLiveInstallerMsiSources or C:Program Files (x86)Common FilesWindowsLiveInstallerMsiSources if you are on x64 Vista.
- Copy the MSI files for the programs you need to the unsupported OS and install them. You will have to guess as to which MSI file is for which program, but that is doable.
The installation on the unsupported OS is completely automated, you will not be asked for any input.
Nice work Microsoft…