After installing Remote Desktop Web Services, one of the first things that I wanted to do was remove the requirement to put the domain name in. I am in a single domain environment and do not have a need for users to have to qualify their domain. I found the following fairly simple fix:
– Find the file renderscripts.js which for me was located in: C:WindowsWebRDWebPagesrenderscripts.js
– Find the function onLoginFormSubmit()
– Find the lines:
if ( objForm != null )
strDomainUserName = objForm.elements("DomainUserName").value;
– Copy/Paste the following code after the lines above:
// add default domain...
if ( strDomainUserName.indexOf("\") == -1 )
strDomainUserName = "YOUR_DOMAIN_NAME\" + strDomainUserName;
objForm.elements("DomainUserName").value = strDomainUserName;
– Save the File.
A new server has been added to the forest as a new domain controller, on the new server after launching PowerShell command line, Use the Move-ADDirectoryServerOperationMasterRole command to transfer all the FSMO roles. Each role corresponding to a number :
Move-ADDirectoryServerOperationMasterRole -Identity “DC01” -OperationMasterRole 0,1,2,3,4
Installing first KMS Server
Below are the steps I used to install the KMS server. We determined that due to the number of client activations, and the capacity of our infrastructure we had no problems installing this server on our secondary domain controller. From here on we will call it DC1.
- On the Domain Controller we run CMD with elevation
- Type slmgr /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx where the last section is the Key from your volume licensing website.
- Open “Windows Firewall with Advanced Security” via Start menu -> Administrative Tools.
- Under Inbound Rules scroll down to “Key Management Service (TCP-In)”, right click and select enable.
- Reboot the machine – note you can restart the Software Licensing service but I preferred to reboot it (seeing as the server was not in use for anything else)
best way to manually remove Exchange 2010 from an organization
Go to Primary Domain Controller
2. Open ADSIEDIT
3. Right Click on ADSIEdit and Click Connect to
4. Connect to “Default Naming Context”
5. Navigate to the following objects and Delete them.
I wanted to setup some programs to run as Windows Services but found information on the subject to be scattered around everywhere. So this post is basically for consolidation and clarification but is not focused on unattended installations.
What is a Service?
A Windows Service is automatically started when your system boots. There is no need to logon to the system. Services also are not affected by people logging off. Services automatically recover from program crashes and Standby and Hibernation modes. Windows 9x/ME do not have a Service facility. Installing software as a Service requires Administrator permissions.
What are the options for running a program as a Service?
This is Microsoft software and is installed by default on XP and 2003. It is probably the best and easiest method but it won’t work if the target executable was not programmed to run as a Service. This rules it out for what many people are trying to do since most programs that are designed ro run as a Service have that option included somewhere in the application. sc.exe is useful for the Unattended crowd, though.
Having installed Veeam FastSCP onto my Windows 7 (64) Ultimate workstation I was getting the error messages Retrieving the COM class factory for component with CLSID [5F1555F0-0DBB-47F6-B10B-0AB0E1C1D8CE] failed due to the following error: 800700c1
How to manually remove an Exchange 2007 that got hosed.
Uninstalling exchange was also unsuccessful because some objects were missing from Active Directory. I also wanted to avoid reinstalling the OS as I have critical software that needs to remain. So I tried removing exchange manually.
- Run setup /m:uninstall (From Exchange 2007 Media)
- Stop and disable all the Exchange 2007 services
- Use Registry Editor (Start->Run->Regedit) to remove these Exchange related registry keys:
- HKLMSYSTEMCurrentControlSetServicesMSExchange* (all the keys starting with “MSExchange”)
- HKLMSOFTWAREMicrosoftWindowsCurrentVersionUninstallMicrosoft Exchange
- Remove the entire Web Server role (don’t forget to reinstall afterwards as it’s a prerequisite for E2K7!)
- Remove the Exchange 2007 server from Active Directory. I ended up deleting the entire “Microsoft Exchange” branch from ADSIEdit (Configuration Container > Services > Microsoft Exchange) as my domain only has one server.
- Use Windows Explorer to delete:
- C:Program FilesMicrosoftExchange Server
- Use Windows Installer CleanUp Utility to remove all the exchange related info from the installer database.
- Remove the security groups created by Exchange setup from AD
Note: Manually removing Exchange 2007 is not supported by Microsoft! Official guidance for removing Exchange 2007 can be found in this TechNet article.
Server 2008 unlike its predecessors, comes with the multiple remote desktop session restriction enabled. If you are only connecting to a server for remote administration purposes that can get a bit annoying, especially if you have a generic administrative account that multiple techs are using, and you keep kicking each other off the server.
Option 1: Enable Multiple RDP sessions from TSCONFIG