Number6

We are scrapping our old domain and scratch building a new one. Squid is currently integrated with AD and transparently authorises users with their AD credentials. How do I reconfigure squid / Dansguardian so that it will recognise the new domain credentials, usernames will be the same, it's just the domain part that will be different. A guide anyone?

Your gut matches with my gut I've been given next to no support over this by line management, except for platitudes stating it won't be an issue. I'm flying by the seat of my pants on this one. I have a strict four working day window in which to do this, and that includes strpping down the cabs, modifying them, installing new UPS', etc, as well as the actual domain migration work. I'm trying to deal with issues as they arise in my mind but, like you, I'm convinced it'll all go pear shaped for lots of reasons. And no fingernails left to chew!

Another question: Is there any need to do anything other than remove all client PCs and servers out of the old domain and into a workgroup? One of our ICT people suggested that I need to give local admin ownership of the C$ share on all machines. Do I need to do this?

I have used subinacl previously, it's a good tool. One of our users lost access to her home folder recently, it was a permission denied problem that cropped up for no apparent reason. Subinacl sorted it without fuss.

Exactly so. Even if we could, we simply do not want the SBS box to be connected once the new servers go live. Paranoid I know, but we've had too many strange AD related problems with it and i don't want even the slightest risk of any issues being imported into the new AD structure.

I know. But we've had a lot of strange problems with the SBS box. It was installed before my time here and has never been right. We don't want to risk importing any AD problems so we're starting from scratch.

I'll take £550 o.n.o. + carriage ?

NOW SOLD

The roll-back plan is to plug the SBS box back in and reset everything Other than that we can't physically move the mailboxes because we don't intend to have old and new servers co-existing at all. We need to export the mail data to a neutral zone and then import it later.

A thousand thanks! Good pre-warning there about something that I was completely unaware of.

Yes, that sounds logical re: SIMS Unfortunately our shared folders are shared by just about everyone.

We do have shared areas on the NAS box and on the SIMS server.

Also, will I need to change ownership or permissions of the .pst files created by exmerge?

Morning! In parallel with my other thread today regarding export - import of Exchange data. I want to make sure that I have all i's dotted and t's crossed before we hit the go button next Monday. We're migrating everyone and everything to a new domain as follows: EXISTING SITUATION SBS2003 - apart from it's DC and Exchange duties it runs WSUS and that's it 1 x Member Server 2008 box running SIMS & Sophos & some file storage. Also acts as a secondary DC 1 x NAS box running Storage Server 2003 - file server. This holds all the users home folders and other data, nothing is stored on local PCs. 1 x Server 2003 print server ~100 client PCs - mainly W7 with a few legacy XP machines 85 users with mailboxes MOVING TO THIS SCENARIO 1 x Brand New Server 2008 R2 Ent DC 1 x Brand New Server 2008 R2 Ent running Exchange 2010 Ent PLUS The 2008 and 2 x 2003 servers in the current scenario. All user accounts have been created on the new DC and mailboxes created on the Exchange Server with same names and logins as originally used. So my plan is to export the Exchange data with Exmerge onto the NAS box, demote the Secondary DC and remove all servers and PCs from the current domain into a workgroup. Add all machines into new domain. Import old Exchange data into new 2010 server. It all *seems* relatively straightforward, however, one of my concerns is data ownership. How can I ensure that the users will be able to access their data? Ownership will have been conferred under the old domain and the SIDs will be different for the newly created users, presumably I will need to transfer ownership of the files to the "new" users but how can I best achieve this? Do I need to take local admin ownership of the server data once the servers are unjoined from the old domain, or do I need to take local admin ownership of the client PC C-drives, or both? How would I achieve this? Apart from the Exchange export and import, data ownership is my biggest concern; I don't want to set everything back up only to find that users can't access their data. Advice would be most welcome at this chewing-fingernails stage please

Has anyone used this? Priasoft - Exchange Migration and Management - Microsoft Exchange 2010 migration and coexistence solutions.