I feel your pain...I once spent 33 hours over three days on the phone with PSS. I had a DC/Exchange box go down and it took that long to get everything back to normal after initial instructions from them screwed things up royally.
Get some rest! Bill Lambert Concuity Phone 847-941-9206 The information contained in this e-mail message, including any attached files, is intended only for the personal and confidential use of the recipient(s) named above. If you are not the intended recipient (or authorized to receive information for the recipient) you are hereby notified that you have received this communication in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and delete all copies of this message. Thank you. -----Original Message----- From: Kurt Buff [mailto:kurt.b...@gmail.com] Sent: Thursday, April 01, 2010 12:18 AM To: MS-Exchange Admin Issues Subject: Re: SBS 2008 SP2, PSS Disaster and on 18 hrs with 5 hrs of sleep the night before Welcome back to the land of the living. On Wed, Mar 31, 2010 at 22:01, <greg.swe...@actsconsulting.net> wrote: > Well God is smiling down on me. Reset the perms and everything powered up > perfectly. Not ideal, but at least I know if there is an install problem in > the future I can track it down using Proc Explorer. Heck, everything is > even running quite a bit faster. > > > > Off to test the workstations and then go eat my now very cold dinner. > > > > From: Greg Sweers > Sent: Thursday, April 01, 2010 12:35 AM > To: MS-Exchange Admin Issues > Subject: SBS 2008 SP2, PSS Disaster and on 18 hrs with 5 hrs of sleep the > night before > > > > Anyone know a way to revert HKCR on an SBS 2008 server to what its supposed > to be. Whatever PSS did, it reset the perms on just about everything to > Authenticated Users and Creator Owner with Read. > > > > Running the RU9.. Whipped out process explorer and exempted everything but > deny errors. Started the install and for about 30 mins jumped to each > registry key to manually take ownership and inherit permissions. That’s > after setting the top level manually but not resetting inheritance. Then I > get to an area that virtually every key is wrong for like 200 down, and many > of them don’t have anything to do with Exchange. > > > > SubinACL is not supported for 2008, PSS…yep called them back…said that may > have happened as a result of what we did, but it wasn’t intentional.. Do > you have a backup??? > > > > Might be dangerous and just reset the inheritance at the top and see what > happens. Trusted installer and several others that are owners shouldn’t be > affected. Cant be any worse than what it is now. Probably going to exmerge > the Exchange data, copy the files and rebuild a new SBS box and move > everything back in.. Joy.. > > > > Rejoin computers to new domain.. Move favorites, reimport..Good thing I > started another SBS install at 4pm when I saw this thing getting bad.. > > > > Greg > > > >