oxide54

are they derivitive from the HP line or the compaq line. ? its confusing cause the ex compaq line is now called "HP Buisness Desktop" and a lot of what is actually hp is now branded compaq. the original compaq line, now "HP Buisness Desktop" lets you change the guid in the BIOS setup. you can tell a compaq derived machine from the custom BIOS its look hasn't changed much in the last 10-15 years, where as HP derived machines have a standard BIOS.

oh and do the "clear PXE advertisement" just in case it started to boot and then failed quickly.

i'm thinking your boot image. is the client x64? do you have both x64 and x86 boot images? is the boot image distributed to the boot image distribution point and the site distribution point ? and \SMSPXEIMAGES$ (apologies if you know this already, but right click on the boot image and select manage distribution points) check the boot image specified on the task sequence. hopefully you'll have it working tommorow.! if not fire any questions, I've just spent the last week getting ours to work and came across quite a few "gotcha's" but its all running smoothly now, except of course the edu-tec machines all supplied with the same GUID

thats correct for cals, I was talking server licensing.

vm is def the way to go. snapshots and all that jazz as well. do your self a favour if you haven't already and download mdt.

what does smspxe.log say? in the SMS_CCM\Logs (under program files or Program files(x86) ) use trace32 from the toolkit. Download details: System Center Configuration Manager 2007 Toolkit V2

can you not force it to 1gb

Correct Computer Name !!!!!!!!!!!!!!!!!

memory make a significant difference on the client, client 1 512mb, client 2: 1500mb started imaging 5 minutes after client 1 and finished 5 minutes before. don't even try with 256mb, WinPE/SCCM/MDT crashes. obviously we would never put a machine on someones desk with 256mb, but that is the default ESX vm memory size for XP, and we sometimes use VM's for testing.

ok so i rebuilt the boot image. set SkipWizard=Yes in sccm_bootstrap.ini i also created a new task sequence. i suspect that the computer name will now be MININT-XXXX and I'm just not being prompted. but we will see when it finishes. (conviently at the end of man poo vs liverpool!)

hi, I am running System Center 2007 SP2 R2 / MDT 2010. and i can't for the life of me get the deployment process to pick up the computer name from sccm, I have imported the PC via computer association / import computer information and entered GUID/MAC/Machine Name. PXE booting is working, it PXE boots into WinPE and then prompts for the computer name (MININT-XXXXX) It also exhibits the same behaviour on an existing machine. i want it to pick up the association from SCCM. i've pressed f8 at that point and checked the SCCM variables. OSDComputerName is set to MININT-XXXXX _SMSTSMachineName is not set. ??????????

to the point where, if you are buying one system center product to run on multiple vm's e.g DPM you may as well get all the suite via enterprise / datacenter licensing.

might be worth waiting. Microsoft are going to announce a slightly different licensing model at BETT next week. ah toby just wrote that!

This is not the weakest argument in the world. If you have to take system offline to update it, it affects its usability and functionality quite a lot.

The last SIMS update required, everyone to be logged out of SIMS, full backup of database to taken. Client workstations updated, (and don't tell me this is automatic.) SIMS workstations updates relies on giving users write permissions to areas of the workstation they shouldn't have. Windows Updates (WSUS) performs these updates in the background independant of the users permissions.

i can see you don't need much when deploying to physical to machines, but surely when using vm's the write cache will cripple a san if your not carefull?

no other software we use requires updating at the frequency that SIMS does.

SIMS and their insistence that I update to the latest version every 3 months

hello mate, all it was, was it looked like a service pack rather than the full release. it was called "service pack 2." coming from the microsoft school of thought ( dangerous I know! ) i was presuming it was the service pack 2 rather than "xendesktop 4 with service pack 2 applied" ! I have since trialled xendesktop and been very pleased. I love provisioning server, its amazing what you can do with it. the only concern I have is hardware driving the IOPS for large scale deployment.

we find killing the exchange profile is good in 98% of places, although the last 2% the whole windows profile is neccesary.

we didn't require any. although we were running office 2003 sp2. you do need to to either configure the outlook 2003 for secure access to exchange 2010 or configure exchange 2010 not secure.# EDIT: sorry just read above posts, but still my post stands it was okay for us with this setup. 77 We found people roaming between outlook 2003 and outlook 2007 more of a problem with the outlook profile getting corrupt.

run the sql in my post above fixed it.

end user recovery is fiddly with DFS shares. DPM 2010 --> No Failed jobs /errors +100

we had problems with overheating using this methods, but this was down to badly designed case/airflow in the computer start with, which was made worse by the only badly situated vents being completely covered by the metal cage!

definetly something that needs "mastering"