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.

No We're creating a totally new AD structure, the new servers will be on a different domain. We're hoping to be able to export the old mailbox data to a neutral location, remove the SBS box, join all old servers and PCs to new domain and then import the mailbox data to the new Exchange server.

Thanks James Why do I need a 32-bit machine though? Can I not export the SBS database and import straight into Exch 2010?

Difficult to find specific information on this. I'm moving approx 100 users from SBS2003 to a Server 2008 / Exchange 2010 based network. What's the best and simplest way to get the email data from one to t'other? All the users and new mailboxes have been created on the new servers. I'm thinking of Exmerging the data off the SBS box and then using: on the 2010 box to put the data onto the new server. Is this method OK? If not is there a better way?

As the title says. It's the latest Orange PAYG Android phone and is an excellent device, there's a review by TechRadar HERE This is literally brand new, unused and boxed. I'm selling it for £70 + postage and this includes £10 call credit on the Dolphin plan which gives 300 texts + "unlimited" internet. First come first served.

Black G2 (T-Mobile version) HTC Hero. Near perfect condition and includes a genuine HTC leather belt case (almost unused and looks near-new), a silicone skin and it has been used with a screen protector from new so no scratches or marks on screen. Locked to T-Mob but can be unlocked for around a tenner I believe. Rooted and currently running Cyanogen 1.6 (based on Android 2.2 Froyo). Can be easily flashed with other ROMs or reset to factory standard if required. I have no idea what it's worth so I'm looking for offers - PM me please?

Yes, I still have the iPad. I had to withdraw it from sale as I suddenly needed it for a particular job at work. The original Sale thread got a little messy so hence this new one. There are pictures Here Anyway, it's for sale again now. 64Gb WiFi + 3G & Otterbox Defender case & an Incipio Kickstand case. Perfect and as-new condition with original packaging. It's been used with a screen protector so screen is also perfect. It's been upgraded to iOS 4.2 Cost new was nearly £800. I am open to a reasonable offer for the job lot + postage by RM Special Delivery at cost. PM me please if you want to make an offer.

Good morning. This concerns volume activation of MS Office 2010. We've installed MS' Volume Activation management Tool (VAMT) v2.0.67.0. on a W7 machine that also runs as a KMS host specifically for Office 2010. We have another KMS host machine in the domain on a server 2008 box that activates W7 - this is not particularly relevant to the problem at hand, just background info. VAMT runs OK and finds all our AD machines. When I run "UpdateStatus" from VAMT it finds and reads all my servers OK and it also reads a very small number of PCs OK, the majority of PCs however generate the following error: On a remote PC: I've checked that the WMI service is running I've enabled DCOM - "Enable Distributed COM" is checked on the Default Properties tab, Default Auth level is Connect and Default Impersonation level is Identify. Com Security Launch and Activation permissions have all four tick boxes checked for the "Everyone" user under "Edit Limits" I've turned Windows Firewall off on the VAMT / KMS host and the remote PC And still I get the "Unable to Connect to the WMI Service" error. VAMT is OK, or it must be as it finds and reads the servers and a small number of PCs OK. Any ideas?

OK, Apple is having a sale then so shall I. £575 all in (iPad + Otterbox case + Incipio case) + carriage (probably £10 or so). It's been upgraded to iOS4.2

I have recently installed spiceworks to test it out to see if it's worth rolling out on a production basis. Installation is OK, at least no errors were generated. I initiated a network scan a week or so ago and it seemed to start OK, a few devices and people were detected and inventoried. It picked up some warranty information, etc, etc. I left it running on the Friday and it then transpired that I was off work the next week. When I returned yesterday I saw that no further information had been logged and the scan page is reporting: And simply keeps repeating this over and over, it's been running overnight with no change. I can't see anything wrong with the settings and the system was obviously working in some fashion when I originally set it up because it has inventoried a certain amount of data. Has anyone else seen this problem? Any tips for resolving it?

Pictures as requested. I haven't taken the iPad out of the Otterbox because it's a fairly involved job. If you're serious and really want to see it dismantled then I'll do it.