Gatt

WTF? They've only just released 4!!

yeah pretty much - we seem to have an issue where profiles aren't being unloaded properly and getting loads of username.domain.xxx folders!! Anyway I gave up with these as our aging Network infrastucture couldn't cope!!

Yeah the x86 version of 2007 was only available during the beta and RC stages, once it RTM'd it was x64 only...

@timbo343 - this is the thread from about a year ago about my migration.. http://www.edugeek.net/forums/windows/54086-advice-upgrade-exchange-2007-2010-a.html

I don't recall having to mess with DNS for this... though I'd rather prevent them from accessing OWA during the transition

Pretty much.. So you will effectively have 2 exchange servers running at once during the moving of mailboxes.. Though don't collapse your 2007 server until you are sure all the mailboxes are over Also, you need to ensure that office has correctly identified the new server - 2007 onwards does this automatically, but think 2003 needs to be manually told about it. Then collapse 2007, rebuild it as 2010 and repeat the process... Once all the mailboxes are back on Atlas as 2010, you can remove your temp server completely...

Least we're giving some poor sod a job then

Its actually quite a smooth transition The new 2010 box will automatically pick up all your existing settings All you really need to do is move the mailboxes across.. I did hit a slight snag with this in regards to some of the system mailboxes.. I'm sure i posted it on here (was about April last year IIRC...) Also, I had to do it twice - once to go from 2007 to 2010, then again when I reformated the old 2007 server to 2010 (eg EX01 -> EX02 -> EX01)

or.. .localhost

could be interesting to buy .intranet and let the mayhem ensue as everyone enters http://intranet/ and gets my website instead

After about 6 months, I have finally resolved a porblem I was having with my SCCM Server where the OS would not fully load and about 95% of services were stopped and there was no Network communication at all Every Monday I have had to: Goto the server Power it off Power it back on wait 5 mins til it checked everything Go into Safe Mode (took about 20 mins as it rolled back the updates (even if there were none!) Reboot Wait another 15-20 mins whilst it again rolled back the updates Log in as normal! No idea why this was happening but it was getting to be a right royal PITA! Anyway, over the weekend I cam across an article on the net somewhere, where someone had had a similar prob to me Solution: Rerun setup and "upgrade" the server to the same edition that is currently installed - this effectively acts like a OS Repair So this morning, after going through my usual monday morning routine, I tried it.. And it worked!! Server has had 3 reboots and all (except one which I am looking into...) services have started as expected!

Isn't that what we expect from The Government anyway?

Freaky!! until I dragged a pic of my broken iPhone and got some very NSFW results and "the stare" from my wife....

Other option is to set WDS to Prompt for admin approval for unknown devices This will then place the Machine the the Pending Devices node and give you an ID number with its MAC Address this will then allow you to rename that PC and add it to AD The deployment pauses until the device has been authourised and then continue with the name you just gave it More info here -> Windows Deployment Services (WDS) « Information Technology Blog

Looking forward to it - chance to get some work done in piece!!

I do pretty much everything with SCCM - Software Distribution, OS Deployment, WSUS and now Forefront Endpoint 2010 definitions....

At the moment, We do that due to lack of anywhere else to put it I did build a Secondary Site at one point and use it as a 2nd DP (Branch?) This may be a better solution if you have a spare box floating about as you can at least replicate the DP across 2 Machines..

At the rate its coming down here, I could swim to the Moon!

It's chucking it down here and there is nothing but thick grey & black clouds as far as the eye can see

Network Drivers? I#ve had this where it PXE boots into WDS/WInPE but then loses its drivers, meaning you may need to inject some drivers into the Boot Image or WIM if its an image file

Yep, ensure that PXE booting is enabled and is in the boot menu via your BIOS - most PCs have PXE enabled as soon as you enable Network Boot in the Boot Order menu, but some (Dell's mainly) have PXE as a seperate option (Why, I don't now as you cannot network boot without PXE!) I usually have it first, with HDD being 2nd (dont boot from CD or USB here as the kids sussed this one!!) It will then prompt you to press F12 to boot, and as long as there is a valid boot file in WDS (Create it in MDT then import it to WDS... Though your Guide should explain that part) Don't worry about it always PXE booting, as it will time out (or if any other key is pressed) at the F12 prompt and try the next device..

Make sure the site-site transporters are configured only for use by ICT Staff only.. any word on the Holodecks and replicators?

Looks a bit like the Citadel from HL2 on its side...

Urgh... (recalls the nightamre of Exchange 2007 to 2010...)

I'd like to see ome Isolinear circuitry and bio-neural gel packs, with the staf all wandering around with Comm Badges... /dreamworld The big issue for me is whether they will move to CC4 or stay on the Gatt Industries Network System ® © (aka Vanilla Network) Quick chat with the HT reveals he'd prefer the latter -