+ Post New Thread
Results 1 to 11 of 11
O/S Deployment Thread, upgradng server in Technical; We are using WDS currently and we are running it with Server 2008 on a fairly old server (IBM eserver ...
  1. #1

    Join Date
    Feb 2010
    Posts
    12
    Thank Post
    5
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    upgradng server

    We are using WDS currently and we are running it with Server 2008 on a fairly old server (IBM eserver xseries 235) and we have about 200 GB worth of space available for all of our district images (we have about 4000 devices to image)

    Right now we have close to 1 TB worth of images. with the space being limited, we copy images over from our external drive to WDS as needed. Very time consuming.

    so we are looking at basically starting over with a new server where we can start off with the right amount of space for our images so we do not have to copy back and forth all the time. What I am working on, to cut down the amount of our images is to inject drivers (something we had not done to this point) so that will cut down on the headache a bit.

    I would not think we would need much as far as server specs go, but we do a pretty good amount of imaging and want something sturdy. My question is, since we will probably be getting a new(er) server, what kind of specs do you think we would need or comparatively, what do you guys currently use for your WDS server?

    thanks for any assistance you can provide.

    steve

  2. #2
    oxide54's Avatar
    Join Date
    Mar 2009
    Posts
    798
    Thank Post
    51
    Thanked 55 Times in 54 Posts
    Rep Power
    23
    a VM on one of my hosts.

    shares with 10+ other VM's on a DL380G5

    have you looked into MDT? should handle driver injection for you.

  3. #3
    mhundley's Avatar
    Join Date
    Oct 2007
    Location
    Worcester
    Posts
    47
    Thank Post
    11
    Thanked 8 Times in 7 Posts
    Rep Power
    16
    1TB seems a massive amount of space, have you looked at using MDT? With this you can have a single image for each OS you require and make any changes using a task sequence.

    What operating systems are you deploying?
    How many different types of hardware?
    Are you deploying software within the image?

    If you want to deploy either Windows 7 or XP it is fairly easy to set up basic task sequences to perform the installation and then let group policy take over for the software deployment. If you are using the same software in most of your images you can import it into MDT and set any silent install switches as required, these applications can then be installed during the installation of the OS. Similarly with hardware, if you have large amounts of the same model then you only need to import the drivers once and the installation will pick the correct ones and inject as build time.

    If you want more information there are plenty of people on here who have got MDT running nicely who will be more than happy to advise you. If you can give some more info on the background of what kind of setup you have then you could have a test system up and running in a short amount of time.

    I know this doesn't answer your original question on hardware but in the schools we support we run MDT on the server in school which has to do everything (DHCP,DNS,AD,File & Print server etc) and even when imaging up to 40 machines at a time there is no noticable effect on the servers.
    Generally all servers we have put in in the last year will have been Dell T610's with between 8-12Gb ram and teamed Intel gig networking.

  4. #4
    DMcCoy's Avatar
    Join Date
    Oct 2005
    Location
    Isle of Wight
    Posts
    3,505
    Thank Post
    10
    Thanked 508 Times in 445 Posts
    Rep Power
    116
    Quote Originally Posted by oxide54 View Post
    a VM on one of my hosts.

    shares with 10+ other VM's on a DL380G5

    have you looked into MDT? should handle driver injection for you.
    As does plain WDS on 2008R2.

    imo 2008r2 WDS is the only version worth using, and it's fine without MDT.

  5. #5
    oxide54's Avatar
    Join Date
    Mar 2009
    Posts
    798
    Thank Post
    51
    Thanked 55 Times in 54 Posts
    Rep Power
    23
    Quote Originally Posted by DMcCoy View Post
    As does plain WDS on 2008R2.

    imo 2008r2 WDS is the only version worth using, and it's fine without MDT.
    it handles driver injection now?

    do you mean into the WIM?

  6. #6

    AngryTechnician's Avatar
    Join Date
    Oct 2008
    Posts
    3,730
    Thank Post
    698
    Thanked 1,214 Times in 761 Posts
    Rep Power
    395
    You don't need to modify the WIM yourself, WDS will inject any drivers you add to it's driver catalog at install time. The only thing you need to modify is the boot.wim to add NIC drivers (if necessary).

  7. #7
    oxide54's Avatar
    Join Date
    Mar 2009
    Posts
    798
    Thank Post
    51
    Thanked 55 Times in 54 Posts
    Rep Power
    23
    thats what i was getting,

    i use sccm so i my wds is "unconfigured" i haven't used wds by itself for a few versions now.

  8. #8

    garethedmondson's Avatar
    Join Date
    Oct 2008
    Location
    Gowerton, Swansea
    Posts
    2,309
    Thank Post
    973
    Thanked 326 Times in 194 Posts
    Blog Entries
    11
    Rep Power
    170
    Quote Originally Posted by szachara View Post
    We are using WDS currently and we are running it with Server 2008 on a fairly old server (IBM eserver xseries 235) and we have about 200 GB worth of space available for all of our district images (we have about 4000 devices to image)

    Right now we have close to 1 TB worth of images. with the space being limited, we copy images over from our external drive to WDS as needed. Very time consuming.

    so we are looking at basically starting over with a new server where we can start off with the right amount of space for our images so we do not have to copy back and forth all the time. What I am working on, to cut down the amount of our images is to inject drivers (something we had not done to this point) so that will cut down on the headache a bit.

    I would not think we would need much as far as server specs go, but we do a pretty good amount of imaging and want something sturdy. My question is, since we will probably be getting a new(er) server, what kind of specs do you think we would need or comparatively, what do you guys currently use for your WDS server?

    thanks for any assistance you can provide.

    steve
    Whilst not in the same league we also had WDS with 3 images. EVentually I got fed up of new machines arriving and drivers being injected. So we upgraded our server to 2008R2 and followed the MDT2010 path. We now have 1 Windows 7 Enterprise image with driver packages allocated to different machines.

    It takes up less space and works.

    Gareth

  9. #9
    oxide54's Avatar
    Join Date
    Mar 2009
    Posts
    798
    Thank Post
    51
    Thanked 55 Times in 54 Posts
    Rep Power
    23
    Quote Originally Posted by garethedmondson View Post
    Whilst not in the same league we also had WDS with 3 images. EVentually I got fed up of new machines arriving and drivers being injected. So we upgraded our server to 2008R2 and followed the MDT2010 path. We now have 1 Windows 7 Enterprise image with driver packages allocated to different machines.
    same as what we do with SCCM, we use WMI queries in the task sequence to decide which drivers to install

  10. Thanks to oxide54 from:

    garethedmondson (10th October 2011)

  11. #10

    Join Date
    Feb 2010
    Posts
    12
    Thank Post
    5
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Thanks for the answers guys. To answer your questions. Let me elaborate. We are a school district with about 14 sites and 4000 computers. We image computers for both staff and students. So we will take one site as an example:

    School A:

    optiplex 745 and 755
    latitude d530

    this is the layout of most of our elementary schools. however we have two images: 1 for d530 and 1 for the two model desktops. what requires a different image is the site specific software such as the SMARTBOARD software (which means two more images) or PROMETHEAN (two more images). This is the same kind of formula for our middle schools.
    our high school has specific software even for labs and there are multiple images for that alone. i would say at the high school there is about 10+ images alone( 1 room for Autocad Suite, 1 image for Maya, etc.) Then take our staff images which are similar to the software on the student machines but different all together.


    If using MDT along with WDS is more beneficial than WDS by itself, I am all for trying it out. I guess I would need to figure out how to translate some of our after desktop scripts into that process.

    would pushing packages to a base image really save time or just disc space?


    Quote Originally Posted by mhundley View Post
    1TB seems a massive amount of space, have you looked at using MDT? With this you can have a single image for each OS you require and make any changes using a task sequence.

    What operating systems are you deploying?
    How many different types of hardware?
    Are you deploying software within the image?

    If you want to deploy either Windows 7 or XP it is fairly easy to set up basic task sequences to perform the installation and then let group policy take over for the software deployment. If you are using the same software in most of your images you can import it into MDT and set any silent install switches as required, these applications can then be installed during the installation of the OS. Similarly with hardware, if you have large amounts of the same model then you only need to import the drivers once and the installation will pick the correct ones and inject as build time.

    If you want more information there are plenty of people on here who have got MDT running nicely who will be more than happy to advise you. If you can give some more info on the background of what kind of setup you have then you could have a test system up and running in a short amount of time.

    I know this doesn't answer your original question on hardware but in the schools we support we run MDT on the server in school which has to do everything (DHCP,DNS,AD,File & Print server etc) and even when imaging up to 40 machines at a time there is no noticable effect on the servers.
    Generally all servers we have put in in the last year will have been Dell T610's with between 8-12Gb ram and teamed Intel gig networking.

  12. #11

    Join Date
    Feb 2007
    Location
    Wolverhampton
    Posts
    331
    Thank Post
    18
    Thanked 35 Times in 33 Posts
    Rep Power
    21
    You could use MDT to push applications with the image install if you need to but a bit time consuming, so this approach is great if time is not a necessity. For me, time is a necessity so we just update our images with new packages and re-capture ready for deployment.

    I understand what you are saying with the multiple versions of apps in different schools but the largest image instal I have is 13gb, and that includes all the basics plus full Adobe Master Collection. If you can get away with it, push out some of the apps with GPO or SCCM



SHARE:
+ Post New Thread

Similar Threads

  1. Server Recommendation Please
    By altecsole in forum Hardware
    Replies: 29
    Last Post: 21st October 2005, 09:15 AM
  2. Window 2003 Server?
    By altecsole in forum Windows
    Replies: 12
    Last Post: 22nd August 2005, 10:06 PM
  3. Exchange Server
    By woody in forum Windows
    Replies: 16
    Last Post: 21st August 2005, 06:52 PM
  4. Windows Storage Server 2003?
    By altecsole in forum Windows
    Replies: 30
    Last Post: 24th July 2005, 07:28 PM
  5. Event Log Every 5 Mins in Windows 2k Server
    By mrtechsystems in forum Windows
    Replies: 11
    Last Post: 26th June 2005, 10:50 PM

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
  •