1

(1 replies, posted in Other)

Hi again,

I have been googling around while clean installing XP on a multiple different hardwares at the same time. And i have found here:
http://support.microsoft.com/kb/828287
information about what does Sysprep not supports. (ea different HALs/Manufacturers).
And then googling further brought me here:
http://www.vernalex.com/guides/sysprep/hal.shtml (again i come across this site^^)
where i see that ACPI PC is the good HAL to chose for a hardware independant image. Bo begin with. Seems like most multi compatible. If u can say so.

As of speaking about my question before. Now after i clean installed XP on both of two different hardwares i was talking about. I saw that one of them has an P4 cpu and the other one Intell Core 2 Duo (well that i knew ofc). And that both of them have ACPI Multiprocessor PC HAL. That would be the reason this image from the one also works on the other. Also this both different PC's are from the same manufacturer. Only the Mobo is different. But then i think if the mobo is different the manufacturer thing is not relevant at all anymore, isnt it? Also i have found info that Sysprep can be done as many times as u wish with VLK. The limited will be for non VLK then i guess.
So can i still think that the not originally installed but imaged PC is kind of slower because the image wasnt installed on it originally? Or not? Because they still have the same ACPI Multi PC HAL. It wouldnt be an issue.
But ok, ill search/test further and see what i dicover.
ty,
Nikolai

Hi guys and girls,
Ladies and gentleman,

I have a little question. Maybe/hopefully someone can help me with that. Just give some suggestion, or rather share some know how. smile
Lets say i have 2 different hardwares. One is a PC with P5GD1-VM mobo. And the ther is the PC with the P5KPL-VM mobo.
I clean install WinXP on one hardware, with all updates etc. And a list of Educational programs. Then i take/make an image of it. Before i ever Sysprep it. (some places say its limited some don't, so i don't know anymore, so i just take an image before sysprep and after).
Now, if i want all the same setup on another hardware. The normal thing to do as i would think would be to do whole the process of Clean Installing and updating and installing the list of the software on the second hardware all over again. Or to make an Hardware independant image. What i have already tried some time ago and it didnt work. I did something wrong i guess. Will try again but another time/or not right now.
So what i have actually tried to do is. I have just put that image that i had cloned from hardware 1 to hardware 2. There were off-course a view drivers missing. But i installed them. And and cloned this image to. Now i have as it seems two images for two different hardwares.
The question is, how kosher/OK is it to do this? I dont know anymore if i had first syspreped or not. Before last time i did it.
Lets say that i have syspreped the installation and made an image of it. And then put it on other hardware. Then added missing drivers and made another image of it. And this image seems to work. Is this OK to do?
Or another situation that im thinking about now. Lets say i just clone this image from hardware one to the hardware two. (Which contains all the EDU software). (and offcourse i made a backup before i will install the EDU software). Add the missing drivers. And then make an BackUp image (containig all the Edu Soft and added drivers, and not sysprepped yet, originated on another hardware). And then just before i want to send it to other same hardware PC(s) where i pulled it from. I sysprep it. Will that be ok?
Any info or manuals on this matter are welcome,
Thanks,
Nikolai

So the sysprep finished. Although it was a lot! longer than normal sysprep.

The first popup i had while sysprep was running was:
'The 3ware Storage Controller Service has now been successfully installed.'

Then the:
Confirm File Replace:
Source: ...
Target: ...
the target file exists and is newer than the source.
Overwrite the newer?

Also it has view times asked me if i wanted to "Continue" or "Stop installation" of some drivers. Was the 'DriverSigningpolicy=Ignore' setting not good or something?

Then it had an error a view times related to some Windows 2003 drivers. With the question of me wanting to install them further or not. Whenever i clicked it poped up back. So i clicked them random yes and no for ten times or something and then it disappeared.

This is the error:
Elxstor Error
The use of this version of the fibre channel storport miniport driver with operating systems other than Windows Server 2003 is not supported. Do you wish to proceed with the installation?

Also had this error:
Windows cannot find ‘C:\Program’. Make sure you typed the name correctly, and then try again. To search for a file, click the start button, and then click search.

Then also the following error:
Files missing,
The file “RtkHDaud.sys” on Realtek HD Audio Installation disk is needed.
Type the path where the file is located, and then click OK.
Copy files from:
P_sound_realtek_wnt5_x86-32_1102\

After a sysprep has finished the PC haven't been automatically shut down. As it happens with an ordinary sysprep. So i shut it down by hand. (Oh, side dote for myself, here an idea, to copy dpsfnshr manually before shuting down, next time, related to the error ill mention further).

Then after deploying the resulting image on an another machine. A laptop. The first thing i get is: "Windows cannot find 'C:\DPsFnshr.exe'. Make sure you typed the name correctly, and then try again. To search for a file, click the Start button, and then ckick Search.'

Also if im not mistaken it doesn t ask me for a computer name.

edit:
I also realized that i might of rebooted PC when it was said not to do. smile

Ok, followed the guide that i linked in my post and it's busy sysprepping for a view hours already. Let's see what it will be in the end. If it ever finishes. smile

Wow, nobody here? smile

Hi guys and girls,

So I’m diving a little bit in to the world of Sysprep, Universal Imaging, and Driver Packs now. Last one and a half year i have used Altiris Deployment Solution for imaging computer classes at our high school. Also use Clonezilla livecd for some time now to backup my home desktop now. Also been looking into trying out FOGproject and possibly replace Altiris DS 6.9 with it. Have also installed FOGproject on a Fuduntu workstation here on my work PC. Dual booting to it to have some kind of a Linux test machine. Installed it but haven’t configured it yet. Left it as is for the time being. Wanted figure out some possibilities to make an Universal Image. Because we have now 3 (22-34-41) classrooms with same hardware. And one more classroom (22) with another older hardware. Then something like 25 administrative PC's with yet another hardware. And 15 laptops with another hardware + 5 with another hardware + another 5 with another hardware. So I often update the students WinXP image for the most part of the PC's, like 100. But the other day when I wanted to update image for another 22 classroom PC's. I was thinking I don’t even know anymore how much settings I have already changed in the updated image. How would I do that on the other image now. This way the idea to make an Universal Image was born.

I have used already made before me pretty slim/cut down Sysprep.inf answer file. And it works. As long as I don’t start jangling with different hardware. I mean, I am not that experienced yet in slipstreaming yet. But the thing is I always (view years ago already) found the idea of slipstreaming very interesting and wonderful. So I’m very interested and willing to learn and learning. smile Well I can be lazy sometimes. Or have not enough time. But in the end I’m willing. And a kind of able I guess. smile (Like one M$ guy (with a penguin t-shirt under his suit ^^ !) at a Win7 course said, to do something you have to be able and willing.) smile

So first thing I was thinking is, let’s just distribute the existing image I have, with all the programs and settings from the main machines, to the older machines. And then see if it works. Ok, it works. With a view drivers missing. So I assumed, if I install those missing drivers manually  sysprep and pull a new image from this. This image should theoretically work now on both hardware’s, where it comes originally from and where I last updated it. But no. It doesn’t. Well I can update the missing drivers and pull an image and this will be working image for this exactly model I last pulled it from. But it doesn’t work (automatically) on another hardware. Even if its originally coming from there. Because I was thinking the image contains the original drivers anyway, why not? smile

But the other day, when I distributed the latest image, that has already been used on 3 different hardware’s. With some issues off course. Like the hdaudbus.sys missing. And while I point it to the i386 directory that I added to the drivers folder on the C drive it is still missing. I created this drivers folder manually. Later added complete copy of drivers CD for every machine I have here to this Drivers folder on the C drive.

So the other day when I discovered the OemPnPDriversPath option for sysprep.inf and I was manually searching for drivers. Driver by driver and adding them to the drivers folder on the C drive. I came across some unknown device that I couldn’t find a driver for. Even after I installed manually all the drivers from the manufacturers website. I went searching for some drivers packs. Because I had already some DVD full of different drivers directories thrown together on this DVD. Some driver packs from some years ago. And if you use Device manager and let it search for the drivers automatically. You will get like 4-5 same drivers in different folders that it finds. So maybe even the same folders repeating on this old DVD. So when I went to search for some nice driver packs on the net. One wonderfully great tool I found was DRP.su. It solved my missing unknown driver issue on a laptop. But even more interesting part is, it brought me here. Because at their forums I discovered that their solution is actually is based on wonderful driver packs from around here. smile I actually wanted to find something like this site for a view years already. smile

So now that I discovered this wonderful site and forums. I discovered another tool. DriverPacks Base. I mean I already knew about slipstreaming and nLite for a view years already. But that’s not really what I’m on to right now. Haven’t used/learned nLite/slipstreaming yet. Because a little bit earlier I had maybe not enough knowledge/desire/need for it. And have been using Linux anyway, for the last view years. I’m also not thinking right now that I would have a lot of time/need to dive quite deep into slipstreaming. But actually had always some desire to make my own multi boot/install CD. Just the thing is if I’m getting into something, I’m getting into it for good. And I don’t think to dive very seriously deep into slip streaming right now. Although I might be already quite there a little bit. smile

So the next logical question for me is how do I use DriverPacks BASE with Sysprep?

That's the main question actually right now for me. Related to creating universal image. So i have googled around for a view days now. And read some basic guides here and there. And landed in this forum part finding a view sticky threads. Related to the question. I have already seen that it's a good idea to use some script to determine and change HAL's. But tried to get away without it. Although I see its necessary. So what do I do about that? Except getting some minor drivers not installed if I deploy image that I have now I get the hdaudbus.sys missing popup. What do I do about that? And also I’ve heard here, in this thread and somewhere else about KTD. What’s that?

For now I’ll be testing out this method, that seems to me to be quite simpler than the rest of the sticky ones here:
https://apps.education.ucsb.edu/wiki/SysPrep
certainly after following it ill figure some more things. But still you can provide me some answers or hints anytime.
I’m basically searching for a sysprep simple method where i can use Driver Packs/DriverPacks BASE to Universalize my XP image.

Thanks in advance,
Sincerely yours,
Nikolai

Thank you for a warm welcome OverFlow. smile

Wanted to ask a question here, but decided to make another thread bout it. smile

Hi everyone,

Just posting here to say hi to begin with. I wonder how didnt i find this place earlier. smile Maybe everything has it's time and place. smile

Im doing tech support. And actually was busy making (or trying to make) universal image for some time now. Using OemPnPDriversPath parameter for sysprep.inf, what is not that wonderfull. I guess DriverPack BASE can be more interesting. Will test it and read more about it the other day.

Actually the funny thing is, i discovered this site after i discovered DRP.su And today i told (on a facebook) one other Russian IT guy i know a littlebit. Like check this out, that's kinda nice site. And he was like, hehe you know i was there a maintainer of the webcam driver pack. And i was like huh, cool, restecpa. smile Maybe its time for me to, to get involved in rebuilding Fuduntu packages or smething. Only its kind of asking time to. And i kind of mostly get enough of working behnd a copmuter at work. So maye its not so good idea to come home and and compile. smile)

So, anyway, have a nice day, smile
Sincerely yours,
Nikolai