Not sure what to do with imaging machine?

[nicholab]

Feeling a complete idiot that I can't build a Windows 64 image quickly and can't even work SCCM auto install. I am not sure what to with imaging a machine should I image the machine with 32bit so it's ready? The issue with this is only 2.5GB of memory shows up and physical address extension does not work to use over 4GB of RAM.

[SHimmer45]

sometimes building an image "quickly" takes alot of time as you look to create packages and answer files to do the heavy lifting.

i dont use SCCM but use MDT and initially the 1st image i made was installed from the server but was done from the install DVD and then captured to get my head around how it worked, (what could i change via an answer file at point of install creation of a default profile etc).

 

From an MDT point of view i would do this (image the process for SCCM is similar to a point)

 

Add chosen OS and arch to Imaging server

create an install sequence pick the OS you added, provide a few basic details

create a capture sequence

add any required drivers (ESP NIC DRIVERS & HDD)

update deployment share create boot media

boot pc

pick your install sequence

OS installed

add required software any local config

reboot / rerun deployment boot sequence choose capture, specify location on the imaging server to store the image

sit back and wait.

 

go to windowsnetworking.com as they have LOADS on MDT/SCCM/WDS deployment methods which are very good.

 

your 32bit OS needs to support and beable to use PAE, these days i would just plump straight for x64 as it works out of the box and your dont get any oddness with windows still running out of resources to allocate memory, also if you have onboard gfx that will also take ram which reduces the overall amount shown.

 

**i have really glossed certain area's but might be useful to get you going

[LeMarchand]

Build a fat image on a VM, blat it out for now (if you're using the same OS as your 32 bit image you can probably get away with just changing the "bit" lines on your sysprep) and work out the SCCM later?

 

Might want to backup/add drivers to the store first.

[Fazza]

SCCM is one of the best things I have ever installed! It's great for creating/deploying images via PXE!

 

Here's what I do:

 

• Create a 'Golden Image' on a VM that is in a Workgroup and the local admin password is blank
  
• Run a Manual Capture to automatically create and upload the 'Golden Image' to the SCCM Server
  
• Add the 'Golden Image' to SCCM
  
• Create Packages of the relevant drivers
  
• Create a Task Sequence to deploy the 'Golden Image' and Packaged Drivers
  
• Boot to PXE on a Client PC and install the 'Golden Image'!
  

 

It's as fast as it takes to install all the software that is part of our Golden Image and pretty much everything else it automatic!

 

[JRA]

Have a stab at FOG? Back in the day when I first saw SCCM I though "funk this" to myself, and never looked back. We use WPKG for software deployment (which is flexible as anything but I don't like, and I'd say you're as good with Group Policy and scripts) and that suits us.

 

Not used SCCM since, but the rumour mill of it being an utter piglet of a thing puts me right off.

[Dos_Box]

Moving to OS deployment forum.