Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Altiris DS & Windows 7

Created: 18 Aug 2009 • Updated: 01 Oct 2013 | 46 comments
This issue has been solved. See solution.

Hey All,

We are a Windows XP based network running Altiris DS 6.9 for HWII imaging. We have never used Vista but we are now looking at deploying Windows 7.  From my research Windows 7 deployment is similar to Vista. I was wondering if anyone has references or advice on the best way to create Windows 7 HWII images?

Regards,

MArk

Discussion Filed Under:

Comments 46 CommentsJump to latest comment

jjesse's picture

DS SP3 provides support for Windows 7.  Havne't done any of it myself so no hints or tips yet

Jonathan Jesse Practice Principal ITS Partners

SOLUTION
RichC's picture

Was DS SP3 released?  I can't seem to find it on the Downloads section...

--->    i'm no stranger to slack, but i'm not a slacker

SOLUTION
kubasa's picture

I do things a little differently than most but I ran across this link a while back when it was on Juice.  You might want to check it out:

https://www-secure.symantec.com/connect/articles/b...

Also, here's another link that I've refered to frequently in the last couple weeks as I was working on our 7 image:

http://technet.microsoft.com/en-us/library/dd349348(WS.10).aspx

SOLUTION
Rdutch12's picture

DS 6.9 SP3 is in beta at the moment, but will provide Windows 7 support.

Rob Hilberding Sr. Consultant ExpressAbility www.expressability.com

SOLUTION
Ryann's picture

Any word on service pack availability?

SOLUTION
Mark Potts's picture

I have downloaded and installed SP3, it is available on the download site now. 

SOLUTION
kubasa's picture

The thing to consider is that you really don't need 6.9 sp3 to deploy Windows 7.  For convenience sake, yes it's nice but in order to make things work you just have to get familiar with ImageX and WinPE.  It really is easy to capture and deploy images once you learn these things.  I'm still on 6.8 and it's working great.   There are two sample ImageX scripts listed on Samples in 6.8 that got me started.  However, I'm still going to move forward with 6.9 sp3 when we are able to move forward.

SOLUTION
Ryann's picture

It's also pretty easy to do a .img install of win7, and you don't necessarily need sp3 for that.  There's just a boot order change that needs to happen in BCDedit, which I inserted as a script that runs in WinPE after the initial install:

REM To fix boot order with BCDEDIT
bcdedit /store c:\boot\BCD /set {bootmgr} device boot
bcdedit /store c:\boot\BCD /set {default} device PARTITION=d:
bcdedit /store c:\boot\BCD /set {default} osdevice PARTITION=d:

That does it for me, anyway.  Otherwise, I get a black screen telling me it can't find winload.

I'm not even really sure what changes were made in SP3, because I have it in a test environment -- I've been running the beta -- and aside from a newer Dagent version, I haven't really seen any benefits to my workflow.

SOLUTION
DaemonPix's picture

Currently we are using Altiris Deployment 6.9 SP3. I am trying to get the Windows 7 HII rolling along but I am having trouble.  After doing some reading and I am thinking editing the BCDedit will do the trick. But honestly I am a bit lost as to exactly where do I need to edit this. WinPE? or Windows 7 boot? Thanks 

CCNA, A+

SOLUTION
Alaa Yehia's picture

hi kubasa

you are using 6.8 with windows 7?

SOLUTION
noodleNT's picture

Now that DS SP3 is out, is the BCDEDIT still needed? Do I need to recapture my master 2K8 images after upgrading to DS SP3?

SOLUTION
Ryann's picture

I'm about to test that this morning with a new .img that's just a clean Win7 Enterprise install that has the new SP3 DSAgent installed, and I'll report what happens.

SOLUTION
Ryann's picture

I checked first on a VM and later on some physical machines, and it appears that the BCDEdit script is no longer needed.

SOLUTION
noodleNT's picture

I can confirm. It is no longer needed on 2K8 or Win7. You can just take that step out of the job. You do not need to build a new image.

SOLUTION
RichC's picture

for Windows 7 images and Altiris deployment as opposed to WAIK, MDT, etc?  I know there's one for Vista, but it seems there are a few differences with 7.

--->    i'm no stranger to slack, but i'm not a slacker

SOLUTION
BrewNinja's picture

Depending on how you installed win7 depends on if you need to use the bcdedit scripts.  Ive been pulling my hair out for the last week and a half trying to figure out why one master image worked, and one didnt.  I finally realized what I did differently.  If you install win7 to a disk without creating a partition, it will create a 100mb recovery/boot partition before the main partition.  Then you must use the bcdedit script and set the partition=d: (not c: even if its your c: partition...the bootmgr must just see d as being partition 2) If you create the partition before you install win7, then you do not need the script.  Glad I finally figured that out.

SOLUTION
EdT's picture

Thanks for sharing that with us - I normally prepare the partition before installing an operating system, but I'm sure I would have been caught out by that one sooner or later.  ;-)

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

SOLUTION
kubasa's picture

Since we're in a completely managed environment and users aren't going to be doing repairs, etc., I blew away this hidden partition on my master image using information from this article:

http://www.shivaranjan.com/2009/05/11/how-to-preve...

If we weren't in a managed environment, I probably wouldn't do this.  Anyway, I thought I'd share for what it's worth. 

SOLUTION
A.Sun's picture

Bitlock function in windows 7 will use this hidden partition. I would think it is better to keep it.

SOLUTION
kubasa's picture

Yeah, we're not planning on using bitlocker, though.

SOLUTION
kubasa's picture

I got to thinking about this and we might end up having a few user with laptops that would or should use BitLocker.  99.9% won't need this in our environment.  In any case, I avoided it because there just isn't any good documentation about how to do this - basically capturing and applying two partitions using ImageX (one of them being hidden).   I've read Microsoft's technet articles and it thoroughly describes the process for a single partitions but it really doesn't indicate how to handle the hidden System Recovery partition.

Worst case, I did figure out out to add the partition back in using this article (http://support.microsoft.com/kb/933246/en-us) but then I have to apply my captured hidden partition overtop of this newly created partition and then run the recovery tool on the DVD.  It's a little hokey but it will work for the few laptops that we have and that's what I have to work with until we upgrade to 6.9 SP3.

SOLUTION
MurrayW's picture

I still use v6.9 SP2, and have been playing with W7 RTM to get it ready for my environment. At this stage I have decided to go with a very basic (driverless) Altiris Image of my system. This includes the 100MB System, xxGB Windows and yyGB Data partition. I am simply issuing commands in the "Duistribute Disk Image" task like "-p1 -p2 -kp3" in order to retain the data aprtition and blow everything else away... which is what we want.

Downside: Can't inject drivers or perform offline maintentnance on the IMG without risking corruption (see "Image Explorer" issues). Taking a size hit as the IMG contains everything including pagefile etc.

Upside: Without introducing MDT/WDS etc, and without forking out for a Windows 2008 Server, we can multi-cast our Sysprepped and generalised images.

Pre deplyment I generate the driver and utility list, post deployment I copy the drivers, setup script, "unattend.xml", "setupcomplete.cmd" etc to the system, then fix the boot manager ready for booting to production. In my particular case I need to set BCDEDIT to change {bootgmr} to partition "C:" and {default} device/osdevice to partition "D:". All works a treat so far.

Now to sort out why the DAgent MSI causes the "setupcomplete.cmd" to stop processing :(

Quote: "I know not what other much is else. But what other else is there?" - ***** (OP hidden as that was too awful! Lol)

SOLUTION
Alaa Yehia's picture

how can i upgrade from DS 6.8 to DS 6.9SP3 without using new licenses.I have tried to upgrade from 6.8 to 6.9 SP3 but unfortunately the licences doesnot work.

SOLUTION
Rick F's picture

I've DS 6.9 SP3 installed, I do a PXE boot to server run WinPE 2.1 bring the image up to server (create image).  The image is 1 partion (tried dual also).  Create image works.  Then try to deploy image using WinPE.  The goes down to workstation but when it reboots I get an error:

Status:0xc000000e
Boot Selection Failed because a required device is Inaccessible

I run the following commands in winpe:

REM Find the system root and append system32 and BCDedit
%SYSTEMROOT%/system32/Bcdedit.exe -set {bootmgr} device BOOT
%SYSTEMROOT%/system32/Bcdedit.exe -set {default} device BOOT
%SYSTEMROOT%/system32/Bcdedit.exe -set {default} osdevice BOOT

Reboot and it boots to windows.  Tried to run the script after imaging in deployment job, does not work even though DS show it ran.  Have to boot to Winpe & run manually. 
Any one have any ideas why my image is not working ?  Get the same error whether I have 1 or 2 partions, or use WinPE or Linux??

SOLUTION
Rick F's picture

Update:  Running script that Ryann listed above, changing the D to a C is working.  Big Thanks to Ryann

REM To fix boot order with BCDEDIT
bcdedit /store c:\boot\BCD /set {bootmgr} device boot
bcdedit /store c:\boot\BCD /set {default} device PARTITION=c:
bcdedit /store c:\boot\BCD /set {default} osdevice PARTITION=c:

But since I'm running 6.9 SP 3 don't know why I need the script?   I was under the impression going to SP3 it would work...  Working now with work around.  I'll keep trying to get it to work correctly and waiting for DS 7 maybe it will work.

SOLUTION
powellbc's picture

 I am still a little confused about when you run this script.  Does it just need to occur before creating the image?

Also, if you have the recovery partition +system partition do you use the script:

REM To fix boot order with BCDEDIT
bcdedit /store c:\boot\BCD /set {bootmgr} device boot
bcdedit /store c:\boot\BCD /set {default} device PARTITION=D:
bcdedit /store c:\boot\BCD /set {default} osdevice PARTITION=D:
Or do you use:
 
REM To fix boot order with BCDEDIT
bcdedit /store c:\boot\BCD /set {bootmgr} device boot
bcdedit /store c:\boot\BCD /set {default} device PARTITION=c:
bcdedit /store c:\boot\BCD /set {default} osdevice PARTITION=c:

In any case, I have tried many variations of these tasks and non seem to work for me.  I always get the dreaded BOOTMGR error.  I specifically tried the straight DS 6.9 SP3 way with the DAgent installed and allowing the DS to fully manage the sysprep process using my autounattend.xml file.  As far as I am concerned this feature is not working as stated (or it needs to be documented better because of the issue with the hidden partition).  I'm extremely frustrated with this.

SOLUTION
Rick F's picture

Have to slipt this in 2 parts will not take in 1 for some reason.

Powellbc, tell me about it, took me some time also.  1st the script to use....  Which script to use depends on your image.  Does it have 2 partitions or 1 single.  Usually by default Windows 7 likes to put 2 partitions on a drive unless it is already partitioned as 1 big drive. So if you have 2 partions you use this script:
REM To fix boot order with BCDEDIT dual partition
bcdedit /store c:\boot\BCD /set {bootmgr} device boot
bcdedit /store c:\boot\BCD /set {default} device PARTITION=D:
bcdedit /store c:\boot\BCD /set {default} osdevice PARTITION=D:

If you have 1 partition use this script:
REM To fix boot order with BCDEDIT Single partition
bcdedit /store c:\boot\BCD /set {bootmgr} device boot
bcdedit /store c:\boot\BCD /set {default} device PARTITION=C:
bcdedit /store c:\boot\BCD /set {default} osdevice PARTITION=C
:
 

SOLUTION
Rick F's picture

Where to put the script?  On DS server create Distribute Disk Image if not all ready done.  After you've completed the basic job,   Select the job under Jobs if not still selected.  Now on the top right side you have the "Discription" window showing the "Distribute Disk Image" under task and under Details shows the path.  
Click the ADD>> button.  The choose "Run Script".  Should be about 4 up from bottom of list.
Run Script Window opens, now you can put it in a file or just paste it in Under "Run This Script".  I just pasted mine in.     Make sure "Windows" is picked under "Choose the script Operating system", beacuse your using winpe to boot client from.   Click "Next"
Script Information window, under "Script Run Location" pick "On the client computer",
Then below where it says Automation Pre-boot environment, I picked "WinPE_32bit".

I did the last step because we had problems with workstations with 64bit cpu booting to 64 bit Winpe when the OS/image is 32 bit and causing problems.  So we boot to 32 bit to do 32 bit image and 64 bit to do 64 bit image, just to be safe.  Never had a problem booting to 32 bit winpe to do a 64 OS/image.

So if you watch the image come down, after the copy to the workstation is complete, winpe will then run the script, note do not touch the mouse of keyboard.  I try to open i believe the admin comand prompt just as the script started to run, and in WINPE which ever window you click on has run priority and the script stopped till I click on its window again.

Good luck

SOLUTION
powellbc's picture

 Rick, thanks for the comments and details.

I have this working but it is all via Scripts deployed via the DS.  Image X use on the DS and Windows 7 does work correctly (the issue is actually the lack of customization ImageX commands).  We need to do it this way because we elected to follow what we assume is the MS best practice:

  1. Partition the disk using diskpart.
  2. Deploy the image to the second partition (this is not possible using ImageX via the DS console AFAIK).
  3. Run bcdboot from the just imaged volume to populate the system partition.
  4. Inject Unattend.xml to the image.

With regards to step 3, this is how Microsoft says to do it and from what we know it is important to do it this way so the system partitions are unique per machine.  We are not using Bitlocker at this time but may some day so we did not want a fleet of machines without this partition or with one that would cause problems down the road.  I don't think this is the same as what is described above with the BCEdit script.  I found this info here: http://technet.microsoft.com/en-us/library/dd349348(WS.10).aspx (kubasa posted this a while ago).

I think it is sort of disingenuous to say DS 6.9 sp3 support Windows 7 imaging.  It really does not, at least not correctly.  If you could simply run ImageX with full control it would be no issue, but since it is setting command line switches and running diskpart on its own it does not work.
 

SOLUTION
kubasa's picture

Powellbc and Rick, are you able to turn on bitlocker without any problems?  I have the imaging portion working going to both partitions just fine but in order to get bitlocker working, I have to use the recovery tool (bootrec) off the DVD and restore the MBR and then bitlocker works just fine. 

Like I mentioned in a previous post, we might have about 50 laptops out of 3100 computers that might use bitlocker so I'm not overly concerned.  I guess what does concern me is why or how my MBR is getting messed up and what else it might affect down the road.

Because we are still at 6.8, I use a whole series of scripts to get this to work so it is a bit cumbersome.  I asked Altiris what scripts they are using in 6.9 knowing full well that someone at Altiris has dealt with this (hopefully) but they basically told me to upgrade which we can't do for a while yet.   Anyway, are you running the bcdedit script before capturing your base (non-sysprepped) image or are you only applying this after applying the image to the computer?  If yes, do you do the same for your deployable image?  Most of all, I'm really curious if either of you are able to turn on bitlocker using whatever scripts you are using.  If you can enable it, I might have to post what I'm doing and see where I'm going wrong.

SOLUTION
powellbc's picture

 We are not using bitlocker.  I will attempt to run a test if possible.  We use PGP for WDE now but if that ever changes we want to be prepared.



Here are the exact steps (each step is a separate script and we are using DS 6.9 sp3):

1.   Format/partition Drive using diskpart.  This creates 2 partitions in the WinPE environment.  C: is a 200MB system partition and the rest (D:)is for the OS.
2.  Apply Windows image to D using this command: imagex.exe /apply "Win7Ent.wim" 1 D:
3.  Run BCDBoot witht his command: d:\windows\system32\bcdboot d:\windows (this step creates the fresh system partition).
4.  Copy answer file to copy D:\windows\panther\unattend.xml and D:\windows\system32\sysprep\unattend.xml tro ensure they are used.

Because we are deploying Windows 7 x64, we had to create 64 bit boot disks for step 3 to work (otherwise it will try to call a 64 bit app in a 32 bit environment because it is actually executing BCDBoot from the just deployed image).


Although somewhat unwieldy, this process works well except that Diskpart ALWAYS fails on the first attempt on a fresh drive.  After a reboot of the system and a rerun of the job it works and everything goes correctly.  Not sure why what is happening.  I tried building a reboot into the job but using the command "wpeutil.exe reboot" but it  causes the machine to reboot in a loop because the task never completes on the DS for some reason.

SOLUTION
kubasa's picture

bcdboot......that's got to be what I'm missing.  Thank you.  I'm off for a couple of days but I will be trying that as soon as I get back.  I really appreciate it!

SOLUTION
powellbc's picture

 No problem, glad to help.

SOLUTION
kubasa's picture

Darn - I really thought this was it.  If I run the bcdboot, then I get an error message "Failure when attempting to copy boot files".  I tried running it before my bcdedit, after bcdedit and running it without including bcdedit but I always get the same error.   I guess I'll keep playing around with this until we can upgrade to 6.9 sp3. 

Basically, I am running the following as a script job and I can upload and pull down images just fine so in reality, I shouldn't worry, right?  The main problem is if I try to turn on bitlocker, then I get an error and have to use the Windows 7 DVD, run bootrec and then life is good.  Not a big deal really because we will only have about 40 or 50 laptop users but it still bugs me that something isn't quite right.

@echo off

net use y: \\server\eXpress
y:
cd software\hotfixes

diskpart /s W7E_disk_prep.txt

format c: /fs:ntfs /v:Reserved /q <dual_boot_prep_answer1.txt
format d: /fs:ntfs /q <dual_boot_prep_answer1.txt /v:

cd y:\
cd WAIK\Tools\PETools\x86\
bootsect /nt60 SYS

cd y:\
cd WAIK\Tools\x86\
imagex /apply "y:\Images\Windows 7\sr_boot.wim" 1 c:
imagex /apply "y:\Images\Windows 7\1_0.wim" 1 d:

d:
cd windows\system32
Bcdedit.exe -set {bootmgr} device boot
Bcdedit.exe -set {default} device partition=d:
Bcdedit.exe -set {default} osdevice partition=d:
Bcdedit.exe -set {default} description "Windows 7 Enterprise"

W7E_disk_prep.txt

select volume 0
remove letter=d noerr
select volume 1
remove letter=d noerr
select volume 2
remove letter=d noerr
select volume 3
remove letter=d noerr
select volume 4
remove letter=d noerr
select volume 5
remove letter=d noerr
Select disk 0
Clean
Create partition primary size=100
Select partition 1
Assign letter=c
Active
Create partition primary
Select partition 2
Assign letter=d
Exit

dual_boot_prep_answer1.txt

Y

SOLUTION
powellbc's picture

Just so you know, don't expect 6.9 SP3 to fix any of your problems.  There seems to be a big duifference between how Microsoft says you should deploy images and the way it is implemented in the Ds for Windows 7.  As it is now I am using a win PE 2.1 boot disk (not 3.0) because they have not added that support yet.

SOLUTION
Rick F's picture

Where not using bitlocker either, we're using PGP, but we don't encrypt the drive till the machine is given to a user.  Might setup a VM and try it.  We had no problems since we starting running the scripts after imaging with DS 6.9 SP3.  But still don't know why we need it.  DS 6.9 sp3 is suppose to work.  We have a single partition also still need bcdedit.exe.  Only problem we are having is with a Dell 960 which will not take a image.  We've a newer Dell 960 which is a few months newer working no problem, but the older keeps locking up.

We use RDeploy (*.exe; *.img)(Test Mode) to create our images, not imageX.

SOLUTION
kubasa's picture

OK.  I just got this figured out for those of you who are not at 6.9, sp3 and thought I would share this information in hopes that this will save someone else a lot of time.  Here’s what I did – I upgraded my bootsect tool within WinPE from version 6.0.6 (Vista RTM) to version 6.1.76 (Windows 7 RTM) so I could use the /MBR flag and it appears that this did the trick.   In reality if I had been using WinPE 3 instead of WinPE 2.1, this probably wouldn’t have happened but because we haven't upgraded - well, we are stuck at WinPE 2.1.   Bootsect for me is located in the following directory: \\server\eXpress\WAIK\Tools\x86\bootsect.exe. 

Additionally, I changed a few things in my script and after testing it, I finally have a fully functioning deployment script for WIM images using ImageX.  I know a lot of folks on this forum are using .img images so it wouldn't apply.  I headed down this path because we were worried about our funds getting pulled for Altiris so I wanted to be ready to use the Microsoft tools if this were to happen.  As such, this is the road were on and now it's working.

Here's my new script job in case others are struggling with this.  Note that I added bcdboot.exe d:\windows and I'm only applying the OS partition and not the System Reserved partition - I received this suggestion from the folks over at one of the Microsoft deployment forums.  This allows Setup to automatically create the System Reserved partition.  I'm using version 6.1.76 for bcdboot.  Also, because we have Dell OptiPlex systems with card readers which creates 4 additional drives that are read by diskpart, I have to run remove letter=d for the first 6 volumes.  On our laptops, I remove d from volume 0 and volume 1 since they don't have any card readers.  The beauty of Altiris is that I can setup a filter and point the filter according to the computer model and point the laptops to a script that only removes the letter from the 2 volumes.  I could use different drive letters and simplify this whole process but I guess I just feel more comfortable using C and D drives (strange hang-up of mine).  In any case, this whole combination of events is making things work to deploy Windows 7 Enterprise AND allows BitLocker to work properly.

net use y: \\server\eXpress
y:
cd software\hotfixes

diskpart /s W7E_disk_prep.txt  (see below txt file below)

format c: /fs:ntfs /v:Reserved /q <dual_boot_prep_answer1.txt  (see below txt file below)
format d: /fs:ntfs /q <dual_boot_prep_answer1.txt /v: 
(see below txt file below)

cd y:\
cd WAIK\Tools\PETools\x86\
bootsect /nt60 SYS /mbr

cd y:\
cd WAIK\Tools\x86\
imagex /apply "y:\Images\Windows 7\1_0.wim" 1 d:

bcdboot.exe d:\windows

d:
cd windows\system32
Bcdedit.exe -set {bootmgr} device partition=d:
Bcdedit.exe -set {default} device partition=d:
Bcdedit.exe -set {default} osdevice partition=d:
Bcdedit.exe -set {default} description "Windows 7 Enterprise"

W7E_disk_prep.txt
select volume 0
remove letter=d noerr
select volume 1
remove letter=d noerr
select volume 2
remove letter=d noerr
select volume 3
remove letter=d noerr
select volume 4
remove letter=d noerr
select volume 5
remove letter=d noerr
Select disk 0
Clean
Create partition primary size=300
Select partition 1
Assign letter=c
Active
Create partition primary
Select partition 2
Assign letter=d
Exit

dual_boot_prep_answer1.txt
Y

SOLUTION
noodleNT's picture

"upgraded my bootsect tool within WinPE"

How did you do that?

SOLUTION
bmalt's picture

Thanks so much for posting.  I just learned a ton from your script, esp. what is going on between bootsect, bcdboot, and bcdedit.

I noticed the win7 version of diskpart.exe has a format command.  Right now I'm running the 5.1.3565 diskpart which does not have format built in.  I wonder if I can get the newer version running on my PE.  Then I could do formatting from within the same disk_prep.txt file, and ditch the two format lines of the script and the extra answer1.txt file. 

Select disk 0
Clean
Create partition primary size=300
Select partition 1
Assign letter=c
Format FS=ntfs label="Reserved" quick
Create partition primary
Select partition 2
Assign letter=d
Format FS=ntfs quick
Exit

SOLUTION
kubasa's picture

Thanks.  Yes, initially I had problems with formatting.  After we finish our migration I intend to streamline things a bit at our end.  I'm a firm believer to leave something alone if it's working so I won't be changing anything until our migration is done in September.  Glad it helped and you are correct that things could be condensed quite a bit.  Once I get things cleaned up, I should post the latest "version".

SOLUTION
payaso's picture

Using ghost to deploy. This bit really helped a lot:

bcdboot.exe d:\windows

d:
cd windows\system32
Bcdedit.exe -set {bootmgr} device partition=d:
Bcdedit.exe -set {default} device partition=d:
Bcdedit.exe -set {default} osdevice partition=d:
Bcdedit.exe -set {default} description "Windows 7 Enterprise"

Now to troubleshoot SEP 11 MR5 installation. I am getting an error 1603 in the MSI log file.

Has anyone tried adding this to the unttend.xml? I have it in the FirstLogonCommands section right after DAgent...
 

SOLUTION
Nikolai D.'s picture

First of all, hi everyone,

I have read all the posts and havent found anything about Linux pre-boot OS.

So here is the situation:
At our department we use Linux pre-boot OS to deploy educational PC's. The reason here for is speed. The Linux pre-boot OS image can be quite small. Most of them (PC's) are the same models. So there is no need for an hardware independendt image yet. Now ive installed Win 7 on one of them (the model PC's). And guess what.. I can pull the image, but after ditributing it back I get the same black screen boot problem. I have to boot WinPE manually from CD to fix it with bcdedit.
Now i have followed the instructions from one of the links here, to make it one big partition installation. And still i get the same problem. And also the problem is, i cannot use bcdedit with Linux pre-boot OS.

So now im still looking for a solution. And need your suggestions. What do you think would be best to do. How can i fix this?

Any suggestions are appreciated.
Have a nice day! :)
Nikolai

<>< = <3

SOLUTION
Nikolai D.'s picture

Okay guys, ive solved it.
This site kinda helped me somewhat:
http://blog.brianleejackson.com/sysprep-a-windows-...

In attachment you also can find basic-sysprep.xml file that worked for me. And some explanation. The explanation is in Dutch, but anyway. Baybe someone can use it.

Oke, here is no attachment so i just paste it here then.

basic-sysprep.xml

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="generalize">
        <component name="Microsoft-Windows-Security-SPP" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <SkipRearm>1</SkipRearm>
        </component>
    </settings>
    <settings pass="specialize">
        <component name="Microsoft-Windows-Deployment" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <RunSynchronous>
                <RunSynchronousCommand wcm:action="add">
                    <Path>net user administrator /active:yes</Path>
                    <Order>1</Order>
                </RunSynchronousCommand>
            </RunSynchronous>
        </component>
        <component name="Microsoft-Windows-Security-SPP-UX" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <SkipAutoActivation>true</SkipAutoActivation>
        </component>
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <CopyProfile>false</CopyProfile>
            <ShowWindowsLive>false</ShowWindowsLive>
            <TimeZone>Romance Standard Time</TimeZone>
        </component>
    </settings>
    <settings pass="oobeSystem">
        <component name="Microsoft-Windows-International-Core" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <InputLocale>nl-BE</InputLocale>
            <SystemLocale>en-us</SystemLocale>
            <UILanguage>en-us</UILanguage>
            <UserLocale>nl-BE</UserLocale>
        </component>
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <OOBE>
                <HideEULAPage>true</HideEULAPage>
                <NetworkLocation>Work</NetworkLocation>
                <ProtectYourPC>1</ProtectYourPC>
            </OOBE>
            <RegisteredOrganization>YOUR ORG</RegisteredOrganization>
            <RegisteredOwner>YOUR NAME</RegisteredOwner>
            <UserAccounts>
                <AdministratorPassword>
                    <Value>ENTER YOUR ADMIN PWD HERE</Value>
                    <PlainText>false</PlainText>
                </AdministratorPassword>
                <LocalAccounts>
                    <LocalAccount wcm:action="add">
                        <Password>
                            <Value>ENTER YOUR USER PWD HERE</Value>
                            <PlainText>false</PlainText>
                        </Password>
                        <Name>tmp</Name>
                    </LocalAccount>
                </LocalAccounts>
            </UserAccounts>
        </component>
    </settings>
    <cpi:offlineImage cpi:source="wim://C:/Win7iso/sources/install.wim#Windows 7 PROFESSIONAL" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

How to create a deployable Win7 image.

Als je klaar bent met installatie van Windows 7 te voorbereiden (tools er op te installeeren enz). Ik heb er bijvoorbeeld een Altiris Agent er als eerste op geinstalleerd. (de Altiris Agent is nodig om de distribution van het image sucessvol te kunnen beeindigen). En dan ook nog de BasicUtilsPack (die je ook in het bijlage gaat vinden) en K-Lite Codec Pack had ik er in onze basic image geinstalleerd.

Eerst een voraal open je het basic-sysprep.xml bestand die je in het bijlage vindt met een of andere tekst editor. (Ik gebruik er Notepad++).

En past je de administrator en user password aan:

basic-sysprep.xml_.scr_.png

In deze gedeelte van het code:

<Value>ENTER YOUR ADMIN PWD HERE</Value>

<PlainText>false</PlainText>

</AdministratorPassword>

<LocalAccounts>

<LocalAccount wcm:action="add">

<Password>

<Value>ENTER YOUR USER PWD HERE</Value>

<PlainText>false</PlainText>

</Password>

<Name>tmp</Name>

Ook de username die wordt gebruikt bij het aanmaaken van het eerste user, kan je aanpassen. Ik heb er TMP gebruikt. (Deze stap, user aanmaken, kan je niet skippen, of tenminste fond ik het niet :) )

Ik heb deze sysprep.xml bestandje oorspronkelijk van Claessens Jean, via Paul gekregen. Wat ik er in veranderd had is:

<ComputerName>*</ComputerName>

In het documentatie van de WAIK staat er dat:

  1. als je er een naam in typt wordt die gebruikt

  2. als je er een ster in typt wordt er een random gegenereerd

  3. als je het leeg laat vraagt die er laater naar

Maar het probleem is: er is een bug. Die vraagt er helemaal niet naar het computernaam. Dus ik heb deze (<ComputerName>*</ComputerName>) gewoon helemaal verwijderd. Zoals ergens op het internet aangeraden was. En zo vraagt die wel naar een computernaam.

(Paul wou graag dat het zo gebeurde, om zo eventueel ook te kunnen zien dat de deploy werkelijk ook goed heeft gelopen. Vooloppig vindt het ook oke. In de toekomst waneer dat je het mij laat zien, hoe dat je het automatiseert. Zal ik het ook eventueel implementeren. ;) )

Dan plaats je deze basic-sysprep.xml bestandje in C:\Windows\System32\sysprep. (Wat goed is de paswoorden zijn gehasht. Dus die mag gerust in sysprep map blijven).

sysprepMap.png

Start de CMD als administrator:

CMDasAdmin.png

En voer deze twee commandos uit:

cd sysprep

sysprep /generalize /oobe /shutdown /unattend:basic-sysprep.xml

sysprepCMD.png

PC gaat uit na het voorbereiden. Trek gewoon een image ervan. En je heeft een gesysprepte Win 7 image.

En dan als je die image wilt deployen. Moet je gewoon een deploy job maken of een andere kopieren en aanpassen. Enige wat deze sysprep niet doet is de PC in het domein zetten. Maar ik heb het opgelost met een configuratieon task toe te voegen bij de job:

configurationTask.png

(Hier voor moet de Altiris Agent wel al in de image geinstalleerd zijn).

Als refference voor meer informatie ivm de sysprep.xml aan te passen kan je het volgende link raadplegen:

http://blog.brianleejackson.com/sysprep-a-windows-7-machine-start-to-finish

(in het gevaal deze pagina ooiet niet meer beschikbaar is, in het bilage vindt je ook een copy paste ervan).

Okay. Sorry for another language. Maybe ill have time to translate it another day. But screenshoots say also alot. So have fun. :)

Ciao
Nikolai

<>< = <3

SOLUTION
JeffreyJRiggs's picture

reviving the old thread...

ok so we do hii imaging on desktops/laptops - amd/intel - dell/hp/lenovo all with one image file and firm in the drivers... we also use linux boot for this.. even on our server 2003 and server 2008 builds.... although our server builds are unattended installs and in addition the 64 bit server unattends are done via winpe....

sooooo..
anyone have a step by step doc that they can share for setting up a windows 7 system.... you know .... from start to finish....
im following this right now.... just to get somewhere... but not sure if this will work... will replacetokens work and add computer name????

what im following
http://blog.brianleejackson.com/sysprep-a-windows-7-machine-%E2%80%93-start-to-finish-v2

SOLUTION
JSHawks's picture

Hi Jeffrey,

Just a quick note, token replacement should work fine.  I use a custom token replacement script with W7 image deployment and have no issues.  Just make sure to copy the final xml file to %systemroot%\windows\panther  or it won't work.

SOLUTION