Category: windows 2008
-
Access Is Denied Message After Sysprep–How To Fix
If before you use Sysprep to prepare a Windows machine for imaging you set the administrators password “User cannot change password” then sysprep will not clear this setting, but will set the “User must change password at next logon” setting. Normally these two settings are mutually exclusive, but in the scenario for sysprep it seems…
-
Starting Exchange When You Have Active Directory Issues
I had a call the other day from a company who had Exchange issues. One investigation it turned out they had a very suspect Active Directory and no-one would admit to what they had actually done to get it in such a state! One server (DC1) would not talk to the other DC’s (Kerberos issues…
-
Restricting Message Sizes in Exchange Server to Low Bandwidth Sites
Exchange Server has a series of different settings for controlling the maximum message size into and around an Exchange organization, but what about when parts of your organization have a considerably lower bandwidth than other parts, for example offices with servers in rural or hard to reach locations and require satellite WAN links or ships…
-
Exchange Log Truncation Failure in a DAG
Today I visited a client who had noticed that no log files had ever been removed after any backup within Exchange 2010 SP1. It was fortuitous that they had enough log disk space for about eight months of log generations. The disadvantage was that we were four months into this time period, so it was…
-
Office 365 and Dynamic Distribution Groups
Updated Dec 8th 2011 to remove reference to LegacyExchangeDN In Office 365 with Hybrid Deployment, if you create Dynamic Distribution Groups on the on-premises Exchange organization, these objects are not replicated to Office 365 via DirSync. Therefore for mailboxes in the Office 365 cloud they will not see the Dynamic Distribution Group in their Global…
-
Adding Routes Using CMAK
I have just put together a Connection Manager VPN client (CMAK) and within it have specified the extra routing information that I needed. When I ran the client I got the following error message and could not find anything on the web with an answer, so here is the answer… Error 1: Connect action to…