redmonster

Hi all Posting here for want of any ideas on a better forum area, feel free to suggest one! I've now come across this on a number of different computers in different sites so thought I'd check to see if anyone else has come across this. The problem occurs when someone tries to forward or print a QCDA email newsletter. In case you've got a bunch of old emails from them, an example is the one sent out by the QCDA on 25/05/2011 with the subject "Test update: Issue 32 - KS2 Teacher assessment reminder, Accessing NCA tools". On trying to print or forward that email, Outlook hangs and will not respond until you end task. I have now seen this on three different computers running different versions of Outlook. If you try and forward the email as an attachment it goes through fine so this is a usable workaround. Also, forwarding via OWA also works ok. It seems to me that there is some content in the email that Outlook tries to fetch when you hit print of forward, which it then cannot access and Outlook being Outlook just hangs instead of giving up. Any ideas? Cheers!

Thanks jsnetman - I was thinking of imaging the current RM server (to provide a way back during the lab phase) and then do the following: build the new server, join domain, promote to DC, transfer roles away from RM server (FSMO + file, print, dhcp etc) and then start uninstalling the RM bits one by one. Is that how you did it (or would recommend doing it) ? It's the "hacking away" that I'm not keen on - if there was a documented / supported migration path I'd be happy to follow it, but what I don't want to end up with is a network with problems that crop up because of RM bits that are left over in AD that become a nightmare to troubleshoot. In the absence of a documented migration path I'd probably be tempted to do a clean install - one that I know will work problem-free, rather than try and save the effort up-front only to spend twice as much time & effort troubleshooting issues later. Are there tools you've come across that help with this or would this migration involve trawling around manually with ADSIedit to ensure all RM bits are cleaned up? Thanks for your help!

Hi all, Just wondering if Hightower / Michael / any others have any particular gotchas they'd like to share regarding migrating away from CC3? We're definitely moving off RM. Fresh hardware, server 2008 R2, fresh client PCs, OS change - the works. We're faced with the option of keeping the existing AD in order to maintain user accounts & not have to rebuild a member server - or just scrap the load and do a fresh AD build. Re-creating users isn't much of an issue but rebuilding an admin server (SIMS) is a step I'd avoid if I could. Are there problems joining new DCs to a CC3-based network? Would you expect a smooth DC promotion and subsequent demotion of the old RM DC or would you just scrap the lot and start from scratch? Will CC3 leave ugly bits hanging around in AD or does it "remove cleanly"? Thanks in advance!