When Policies Were To Much

[sullivang]

Once there was a happy little network of Windows Server 2003 and Windows XP SP1. Then the big bad govvy god came in and declared "Thus shall you use these settings and make your Default Domain Policy as this. Thus shall you use these other settings and make your Default Domain Controller Policy this." So I being the good little worker bee made the changes. Then he said "henceforth shall you upgrade your systems to Windows XP SP2." And I did. But secretly I only did one or two, 'cause I had learned the folly of such moves. It was not long before the first dragon reared its ugly head. When I tried to install some new software the Windows Installer would think I was in Safe Mode or else something was wrong. This was indeed a problem. Never again on a XP SP2 system would I be able to install or upgrade software. I sent my knights upon many quest to the Google Kingdom, the Dark World of MS Support, and many unexplored, never used realms. Alas they all came back empty handed. Oh they had a trick here or a potion there, but the mystery of XP SP2 and software installation remained trapped by the dragon. Then I held a rebellion. I cast aside the govvy god polices and returned to Win Server 2003 policy defaults and simpler times. The dragon could not take this and slipped away in the night. And the mystery left with him. Now the merry systems of the Realm are happily waving their XP SP2 flags. New software citizen that now come to live here are happily installed and joyfully do our bidding. But at night when the day is done, we often sit and talk about the dragon and the mystery. And no one has ever been able to figure out how he had a hold on software installations and a few other odd shadows. We often ask, "perhaps there is some great and powerful Wizard out there that might know which policy or combination thereof would have caused such a delimma." Perhaps he or she is you. :?: But until then we slowly apply a policy here and then there, building the walls of defense with care and much testing. We know the govvy god will return one day and won't care about the age of the dragon and the mystery of installation. But we will be ready. His dictates will be in place, except for perhaps one or two that won't let the Win Installer work its magic.

[graycat]

a good tale there, mate lol

what was in the default domain policy they foced on you?

Tim.

[sullivang]

Hello graycat,

These were custom settings. I had this long list covering each and every component of of the Default Domain and the Domain Controller Security Settings. Each and every item was either enable or disabled and most had some account added or removed. It was a long tedious task that resulted in a problem. So, no I did not have to load hisecdc or one of the prefab policies. This was all custom. It would take some time and I am not sure the moderator would want me to, but I could load in the settings to the forum.

Moderator let me know if that is ok.