The problem: You’re making changes to Exchange, and it’s scary because the settings are all in AD and if you break something you’re going to have to restore from a System State backup. You want to be able to back up and restore the configuration without having to take down your domain controller.
The problem: Some users were having issues with Region and Language settings – dates the wrong way around, getting the English (United States) dictionary instead of English (Australia). The server is set up correctly, but some users seem to have settings in their profiles causing problems.
The problem: This one took a fair bit of figuring out at the time, as the symptoms were varied and hard to trace back to the eventual cause. This occurred on an RD farm running Windows Server 2008 R2.
- Some users may fail to load their profiles on logon with the below error;
Windows cannot load the locally stored profile. Possible causes of this error include insufficient security rights or a corrupt local profile.
DETAIL - Insufficient system resources exist to complete the requested service.
- The DEFAULT registry hive is growing very large in size (over 1GB)
The registry files can be found under the following folder – C:\Windows\System32\config
- You may have Samsung printers installed with an older driver version
In my case, the issue eventually turned out to be a couple of Samsung printers the client had installed. Every time a user logged on, it would create registry values under the following location in the default registry hive:
As these were not cleared on logout, they just kept building up over time, to the point that the DEFAULT hive was just too large for Windows to handle. A certain amount of users were able to log on successfully, but once a certain number of users was reached they would not be able to load their profiles.
You can confirm this is the issue by using the dureg utility to check the size of the ‘DevModes2’ key, or alternatively just expand the key in regedit. If it causes regedit to freeze temporarily when you click on the key, chances are it’s the culprit.
The problem: You’ve just upgraded to Exchange 2010 or higher and / or enabled Online Archiving for your users. You’ve got a whole bunch of PST files to import for the users and no patience for typing in commands.
The problem: After migrating some users to RDS servers running Windows Server 2012 R2, they realised that they are no longer able to shadow each others’ sessions. Research indicated that this would be difficult to get around for a couple of reasons;
- Shadowing users can only be done via Server Manager – there is no ‘tsadmin.msc’ which can be given to users as a shortcut
- Some hard to grant permissions are required in order to query the RD Connection Broker without being granted Domain Admin privileges
The problem(s): Oh, the problems. Out of the last 3 RDS deployments on Windows Server 2012 R2 I’ve been involved with, precisely all of them have had problems with network printers. Some of the issues you might face;
- Printing from Adobe Reader will occasionally give users the following error
- Duplicate printers which you cannot remove
- You can set the default printer, but it will not display the default printer ‘tick’ icon
- The default printer setting may not be retained, or the printers may not map correctly for all users on logon
The problem: Due to issues with network printing on Windows Server 2012 R2, I decided to move from network printers to local printers on each of my client’s Remote Desktop servers. To make the transition easier for users, I needed to find a way to change the users’ default printers automatically to the local printers.