Some n00b questions volume II
Greetings,
After playing around with OSD like a month (test LAB), I still have some issues;
1. I never manage to join computer to domain while installation. I'm using old hardware (HP d530 desktop, HP nc6220 laptop and VMware guests) and I'm sure WinPE 3.0 supports native network card drivers. I always can access network when task sequence fails
(press F8). What are the depenses of this function?
2. I would like to install multi-boot computers with Windows XP and Windows 7 included. For production it is crazy idea, but for test lab with physical machines it would be perfect. I created custom task sequence which covers same steps twice as default
OS installation from .wim. First I do partition and format with 2 partitions, and then applying XP -> configmgr client -> applying Win7 -> configmgr. Last result I has was that Win XP were installed until the end, but Win7 never started. Is multi-boot
installations even possible with task sequence? Next I'm going to try advertisin Win7 installation on Windows XP computer without cleaning the disk.
3. Driver package cannot be applied with HP d530 installation. I made sure what spesific drivers this desktop requires in XP, and published these only in SCCM's drivers and drive package. Installation of driver package fails.
I could link here some screenshots and logs if that helps.
November 22nd, 2010 2:55pm
1. check netsetup.log in c:\windows\debug, what does it say about the domain join failure ? try removing any OU's specified, and remember the computer container is not an OU so specifying it will fail.
2. not a good idea, not supported, don't even bother trying, you can only have the configmgr client on one os per machine otherwise it will have incorrect infomation in the configmgr database, think about it...
3. what failure is highlighted when you try to install the package, what does smsts.log say ?
cheers
niall
My step by step
SCCM Guides
I'm on Twitter > ncbrady
Free Windows Admin Tool Kit Click here and download it now
November 22nd, 2010 3:02pm
1. I'll get back back with this later.
2. Hmm, I had earlier manually installed a physical computer with dual OS, both had SCCM clients and there was no problem with software deployment on both of them. Perhaps I did change MAC adress manually on one of them, can't be sure.
3. Failed to provision driver. Code 0x80091007. The operating system reported error 2148077575: The hash value is not correct.
November 22nd, 2010 3:22pm
2. it's not impossible, just really unsupported and not a good idea, the configmgr db will have conflicting info about many things, not just the OS. - avoid it.
3. try deleting the package from the dp, re-create it, redistribute it to the dp's
My step by step
SCCM Guides
I'm on Twitter > ncbrady
Free Windows Admin Tool Kit Click here and download it now
November 22nd, 2010 3:33pm
Is there any best practice documentation for drivers? Or is Windows XP deployment really so challenging with just a OSD of SCCM?
Now I get a situation when applying drivers stage complites without an error, but drivers are not applied. They are saved to c:\drivers\1,2,3 etc. but local administrator must run finding new hardware wizard to apply the drivers.
I understand that there is a 2 ways to use Drivers in SCCM OSD - create driver packages or publish drivers to database. Which is more reliable?
Last time I did this like that;
1. I downloaded every driver to my model (HP Compaq d530 and HP Compaq nc6220)
2. I extracted all drivers and exes to folders.
3. I published them in Drivers-section (not Driver Package)
4. I created a category for each model, like 1.category=d530, 2.category=nc6220
5. Task Sequences I created, are model based, there is one task sequence for every model
6. Applying Drivers in task sequence are linked to model based category
Now the problem is with HP Compaq nc6220 model - after rebooting Windows XP during installation it goes to BSOD 0x0000007B which referes to lack of Mass Storage drivers. But there is no IDE hard disk driver for this laptop, is there? Manual Windows XP installation
does not require any additional drivers during installation. Why OSD requires this? And how I can find the mass storage driver for this model?
November 29th, 2010 12:09pm