http://www.windowsitpro.com/authors/author/author/5064694/rsscomment/5064694en-USSun, 27 May 2012 06:00:27 GMTSun, 27 May 2012 06:00:27 GMThttp://www.windowsitpro.com/article/exchange-server/how-to-uninstall-a-stubborn-exchange-server#commentsAnchorMon, 06 Sep 2010 17:47:39 GMT
Murat, I agree with you. I’ve been through the process of upgrading 8 exchange 2010 servers to SP1 and half of the servers were left in an unusable state. /M:RecoverServer did nothing to help the situation and all the cryptic powershell errors when upgrading/uninstalling helped very little. I believe that MS has tunnel vision in their newer products and assume an absolute clean slate infrastructure. Well in the real world, I’ve yet to see a single infrastructure without issues or that conform to the MS mold of thought (which has changed through the years btw). Astrid, if you live in the land of labs and perfect scenarios then what you say is true. Oh, and contacting support comes with a cost. It is easy to make that recommendation if you are on the inside collecting that cost.]]>LoeberMon, 06 Sep 2010 17:47:39 GMThttp://www.windowsitpro.com/article/exchange-server/how-to-uninstall-a-stubborn-exchange-server#commentsAnchorhttp://www.windowsitpro.com/article/exchange-server/how-to-uninstall-a-stubborn-exchange-server#commentsAnchorWed, 14 Jul 2010 02:27:17 GMT
Hello my teacher,
Thank you for sharing this important point.]]>ARICIWed, 14 Jul 2010 02:27:17 GMThttp://www.windowsitpro.com/article/exchange-server/how-to-uninstall-a-stubborn-exchange-server#commentsAnchorhttp://www.windowsitpro.com/article/exchange-server/how-to-uninstall-a-stubborn-exchange-server#commentsAnchorWed, 26 May 2010 10:21:56 GMT
Dear Astrid,
I’m very disappointed with your warnings. The procedure outlined in the article is a working and proved procedure. As I stated in the article, I used this procedure several times without any problem.
Your recommendations are useless because this procedure should be used after regular attempts to uninstall the Exchange Server. If your articles would be a cure I could use them already.
You’d better focus on making Exchange Server a great product again. To criticise working procedure found by the soldiers in the field should not be your focus.]]>murat yildirimogluWed, 26 May 2010 10:21:56 GMThttp://www.windowsitpro.com/article/exchange-server/how-to-uninstall-a-stubborn-exchange-server#commentsAnchorhttp://www.windowsitpro.com/article/exchange-server/how-to-uninstall-a-stubborn-exchange-server#commentsAnchorThu, 20 May 2010 18:25:12 GMT
These instructions are unsupported for both Exchange 2007 and Exchange 2010. Although they may work or appear to work, youll put yourself in an unsupported state that would require you to rebuild the server from scratch before you can re-install Exchange. As such, Microsoft advises readers to not attempt the process outlined in this article.

The supported process to recover a lost or orphaned Exchange server and then decommission it is a two-part process that starts with running server recovery for Exchange 2007 (http://technet.microsoft.com/en-us/library/bb123496(EXCHG.80).aspx) or Exchange 2010 (http://technet.microsoft.com/en-us/library/dd876880.aspx). Then, you perform an orderly uninstall of Exchange 2007 (http://technet.microsoft.com/en-us/library/bb123893(EXCHG.80).aspx) or Exchange 2010 (http://technet.microsoft.com/en-us/library/ee332361.aspx). If these processes are not successful, we recommend that you contact Microsoft support for assistance (http://support.microsoft.com/ph/13965#tab6 ) ]]>Astrid McClean (MS)Thu, 20 May 2010 18:25:12 GMThttp://www.windowsitpro.com/article/exchange-server/how-to-uninstall-a-stubborn-exchange-server#commentsAnchorhttp://www.windowsitpro.com/article/exchange-server/how-to-uninstall-a-stubborn-exchange-server#commentsAnchorMon, 26 Apr 2010 10:25:17 GMT
this is a great way of removing exchange but I would highly recommend you research Why you can not uninstall from the control panel first. Many times there is a good reason why it will not uninstall. a user account still on a database, or a Deleted mailbox that has not been purged. in some cases there are mailboxs that are not as obvious that may keep this from happening. and if they are "hard removed" will cause problems later. So research first. Then use this as an Absolute last resort. ]]>RobersonMon, 26 Apr 2010 10:25:17 GMThttp://www.windowsitpro.com/article/exchange-server/how-to-uninstall-a-stubborn-exchange-server#commentsAnchorhttp://www.windowsitpro.com/article/permissions/ntfs-inheritance-rule-change#commentsAnchorWed, 16 Dec 2009 01:26:49 GMT
Slemmesmi, there are two cases: 1) Legacy clients (2000, XP and 2003) may access the files remotely thru the shares and move the files from GUI. In this case, the former inheritance rule is applied; that is, if the files are moved to a folder on the same disk partition, they do not acquire the new folder’s permissions, they keep their original NTFS permissions. 2) New clients (Vista, 2008 and Windows 7) may access the files remotely thru the shares and move the files from GUI. In this case, the new inheritance rule is applied and the files acquire the new folder’s permissions. Yes, it is very confusing and may result in some unexpected file operations. It is a shame Microsoft hasn’t explained these point widely.]]>MuratWed, 16 Dec 2009 01:26:49 GMThttp://www.windowsitpro.com/article/permissions/ntfs-inheritance-rule-change#commentsAnchorhttp://www.windowsitpro.com/article/permissions/ntfs-inheritance-rule-change#commentsAnchorMon, 14 Dec 2009 02:45:20 GMT
Very interesting read indeed! Question (also in respect of the comment by tovod-everett) is then if the desired behaviour (a move does cause inheritance updates of NTFS permissions of the moved object(s) to those of it’s new parent) in a scenario with a Windows Server 2008 SP2 (e.g. Enterprise Edition) with File Services Role hosting file shares and Windows 7 clients; i.e. when a user on a Windows 7 client, move a folder/files within a file share hosted by the mentioned server on it’s "same" disk? As I haven’t yet got a Windows 7 client I can test this with in my productive environment, would llike to learn from your experience/knowledge.]]>SorenMon, 14 Dec 2009 02:45:20 GMThttp://www.windowsitpro.com/article/permissions/ntfs-inheritance-rule-change#commentsAnchorhttp://www.windowsitpro.com/article/permissions/ntfs-inheritance-rule-change#commentsAnchorWed, 25 Nov 2009 02:14:07 GMT
Thanks for this important info]]>Jean-MarcWed, 25 Nov 2009 02:14:07 GMThttp://www.windowsitpro.com/article/permissions/ntfs-inheritance-rule-change#commentsAnchorhttp://www.windowsitpro.com/article/permissions/ntfs-inheritance-rule-change#commentsAnchorTue, 24 Nov 2009 19:18:41 GMT
Testing under Windows Server 2008 SP2 shows that this behavioral change only affects moves done using the GUI. If you move a file or folder from a Command Prompt using the move command, the permissions do not get updated to reflect the permissions in the new location. Microsoft evidently decided to modify Explorer so as to compensate for the underlying issue, but did not modify the behavior of the underlying APIs. This is understandable given the complexity of modifying the underlying file system behavior without sacrificing the atomic nature of moving files and folders. If you are running Windows Server 2008 file servers but still have users on XP and they do moves using the GUI, the permissions will be improperly inherited because Microsoft left it the responsibility of the GUI to fixup the permissions. See the Perl module Win32::Security for a tool that can assist in identifying improperly inherited permissions that result from moves between locations with dissimilar inheritable permissions.]]>TOBYTue, 24 Nov 2009 19:18:41 GMThttp://www.windowsitpro.com/article/permissions/ntfs-inheritance-rule-change#commentsAnchor