+ Post New Thread
Page 7 of 10 FirstFirst ... 345678910 LastLast
Results 91 to 105 of 139
O/S Deployment Thread, Tips for beginners in Technical; My understanding of this is as follows now. 1) Set up WDS for capture and deploy (Done) 2) Make an ...
  1. #91

    Join Date
    Aug 2008
    Location
    Los Angeles
    Posts
    9
    Thank Post
    1
    Thanked 1 Time in 1 Post
    Rep Power
    0

    Thumbs up Simplify Your Deployment

    My understanding of this is as follows now.

    1) Set up WDS for capture and deploy (Done)

    2) Make an ideal XP image with driver repository on C: and sysprep it with minisetup enabled and Re-Seal.

    3) Boot from PXE and capture the image to the server.

    4) Specify a WDSClientUnattend.xml for the server which will pick the deply image and select the .WIM in the correct image group after partitioning the drive. The partitioning is working and the right image .wim is being pulled down so I'm pretty sure I'm right to here.

    5) Place an sysprep.inf in the correct folder to automate the installation of the image. It gets placed on the boot drive once the .wim is extracted ready to control mini setup.

    It is placed in \\wdsserver\REMINST\Images\Imagegroup\imagefilenam e\$OEM$\$1\sysprep

    6) Boot PC from PXE and it should arrive at a ctrl+alt+del to log on screen after 20mins ish connected to the domain and ready to go.

    7)tear out hair because it doesn't.

    I did not find it necessary to have a driver repository when using WDS and WIM's. Think of wim images as ghost images, they retain all drivers. Also never had to place my sysprep anywhere other than the root of the WIM image.

    You can drasticlly simplify your process by adding a couple of batch files that use tools like netdom(binding), reg add/delete, curl (for renaming via DB's) and last but not least Great Work on the Unattended.XML!!!

  2. #92

    plexer's Avatar
    Join Date
    Dec 2005
    Location
    Norfolk
    Posts
    13,267
    Thank Post
    613
    Thanked 1,567 Times in 1,407 Posts
    Rep Power
    412
    Can someone do an idiots guide to getting WDS setup for imaging and deploying XP machines?

    Ben

  3. #93
    ChrisH's Avatar
    Join Date
    Jun 2005
    Location
    East Lancs
    Posts
    4,996
    Thank Post
    120
    Thanked 280 Times in 258 Posts
    Rep Power
    106
    Ok I need to inject some Network card drivers into the boot.wim so I assume I should be using the Vista Drivers?

  4. #94
    ChrisH's Avatar
    Join Date
    Jun 2005
    Location
    East Lancs
    Posts
    4,996
    Thank Post
    120
    Thanked 280 Times in 258 Posts
    Rep Power
    106
    Ok I have been injecting alsorts of drivers to no avail. Has anyone done any Compaq 6820s Laptops?

  5. #95
    ChrisH's Avatar
    Join Date
    Jun 2005
    Location
    East Lancs
    Posts
    4,996
    Thank Post
    120
    Thanked 280 Times in 258 Posts
    Rep Power
    106
    Thats ok just all ignore me see if I care!!!!! I finally got the network going as it wasnt doing it automatically I had to type in startnet.cmd .

  6. #96
    ChrisH's Avatar
    Join Date
    Jun 2005
    Location
    East Lancs
    Posts
    4,996
    Thank Post
    120
    Thanked 280 Times in 258 Posts
    Rep Power
    106
    It can access all those services on another server.

  7. #97

    Join Date
    Apr 2008
    Posts
    405
    Thank Post
    22
    Thanked 13 Times in 10 Posts
    Rep Power
    15
    I've just started trying to implement this and have spent a day or so pouring over various step by steps etc.

    We are running WDS on a Server 2003 box and I can PXE boot to it from one PC without a problem, but there is another PC which completely ignores it. From what I can see the settings are correct for both.

    Another question, is there a way to get the automated name generation to do incremental letters rather than numbers?

  8. #98
    browolf's Avatar
    Join Date
    Jun 2005
    Location
    Mars
    Posts
    1,524
    Thank Post
    106
    Thanked 88 Times in 74 Posts
    Blog Entries
    46
    Rep Power
    40
    WDS, that deploys XP to x102', p320s, other newer fujitsu's works perfectly.

    trying to deploy to X101 and it bombs out of litetouch.wsf / wpeinit
    discovered the /debug:true mode on it

    the log is

    Successfully changed C: to M:
    No task sequence is in progress
    Successfully cleaned up existing C:\Minint directory
    Starting minimized command prompt
    ZTI ERROR - Unhandled error returned by Litetouch: (-2147023441)
    ZTI ERROR - Unhandled error returned by Litetouch: (-2147023441)

    any ideas?

  9. #99
    browolf's Avatar
    Join Date
    Jun 2005
    Location
    Mars
    Posts
    1,524
    Thank Post
    106
    Thanked 88 Times in 74 Posts
    Blog Entries
    46
    Rep Power
    40
    we're figuring that the x101s dont have enough memory.

    next problem is, something is set wrong somewhere as it only does refresh type deployments, if i try and do a "new computer", it doesnt join it to the domain.
    tried to get a DP Type page in the wizard but it seems to be ignoring SkipDeploymentType=NO.

  10. #100
    DrPerceptron's Avatar
    Join Date
    Dec 2008
    Location
    In a house
    Posts
    908
    Thank Post
    34
    Thanked 131 Times in 111 Posts
    Rep Power
    40
    Does anyone store their WDS Images on a mapped network drive?

    If they do, does it have any major problems (other than the obvious one(s))?

  11. #101

    Join Date
    Apr 2008
    Posts
    405
    Thank Post
    22
    Thanked 13 Times in 10 Posts
    Rep Power
    15
    So you have your images on ServerA and WDS on ServerB?

    Or is the Images folder just a Network Share?

  12. #102
    DrPerceptron's Avatar
    Join Date
    Dec 2008
    Location
    In a house
    Posts
    908
    Thank Post
    34
    Thanked 131 Times in 111 Posts
    Rep Power
    40
    It's a virtualised WDS box now and there's not a lot of space left in the disk groups... but the SAN we have has plenty of space...

    Just wondered whether it's feasible to use that space easily?

    EDIT: Seems WDS does not let you do it without looking at iSCSI...

  13. #103

    Join Date
    Apr 2008
    Posts
    405
    Thank Post
    22
    Thanked 13 Times in 10 Posts
    Rep Power
    15
    When you add an image to WDS it copies it into it's internal folder structure and that can't be changed (as far as I know). Also (and this is just observation I haven't read anything to back this up) WDS seems to adjust the image into different files and if you have two images that are near identical, it takes all the identical stuff and merges that into one file and will then create separate files for each image based on the differences.

    If you look in your images folder on WDS it has a big file called Res.RWM and then smaller files with the image name e.g. OctImage01.wim


    Please correct me if I'm wrong on any of this.

  14. #104

    Join Date
    Nov 2007
    Location
    Manchester
    Posts
    206
    Thank Post
    2
    Thanked 13 Times in 7 Posts
    Rep Power
    16
    I've hit a snag with injecting network drivers into my XP Deployment image.

    I've successfully icaptured HP dc5700 and dc5800 desktops (and had to do the shift f10 thing to install vista network drivers to do the capture of the 5800) and the images works fine and can be rolled out OK.

    Trying to do a HP 6730s laptop today. I've captured the image fine (again having to supply vista drivers prior to the capture so it could talk to the WDS server), but now when trying to deploy its failing to connect to the WDS at the point I should be choosing my image saying that it doesn't have the vista drivers in the PE Image.

    So on the WDS I've mounted the .wim (exported from the WDS) using ImageX

    imagex /mountrw d:\Temp\boot.wim 2 d:\Temp\Mount

    which is fine but when I try to inject the drivers

    peimg /inf=d:\Temp\Driver\*.inf /image=d:\Temp\Mount

    I'm getting the error

    "the image directory specified is not a valid windows pe image"

    WDS is running on Server 2003 SP2 with WAIK 6000.16386.061101-2205-LRMAIK_EN installed.

    Any help would appreciated as I could really do with getting this working..... or at least understanding why its not working!

    Cheers in advance.

  15. #105

    Join Date
    Apr 2008
    Posts
    405
    Thank Post
    22
    Thanked 13 Times in 10 Posts
    Rep Power
    15
    Quote Originally Posted by TheFopp View Post

    imagex /mountrw d:\Temp\boot.wim 2 d:\Temp\Mount

    which is fine but when I try to inject the drivers

    peimg /inf=d:\Temp\Driver\*.inf /image=d:\Temp\Mount


    have you tried doing it without /image=d:?
    From the instructions I have seen the command

    peimg /inf=d:\temp\Driver\*.inf Temp\Mount

    Should do it as you have already specified where the image is mounted to in WinPE

SHARE:
+ Post New Thread
Page 7 of 10 FirstFirst ... 345678910 LastLast

Similar Threads

  1. [RIS] Tips for beginners
    By tarquel in forum O/S Deployment
    Replies: 102
    Last Post: 8th July 2009, 04:23 PM
  2. sims administrators for beginners
    By thegrassisgreener in forum MIS Systems
    Replies: 17
    Last Post: 30th November 2007, 04:42 PM
  3. C# Beginners Courses
    By Stese in forum Coding
    Replies: 1
    Last Post: 29th June 2007, 05:29 AM
  4. Free Linux Course for Beginners
    By CyberNerd in forum Courses and Training
    Replies: 6
    Last Post: 29th October 2006, 08:00 PM
  5. Beginners Guide to Macs
    By nawbus in forum Mac
    Replies: 7
    Last Post: 5th October 2005, 10:31 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •