Thursday, December 04, 2008
Deployment Forum HomeDeployment Forum ArticlesDeployment Forum Download LibraryDeployment Forum Member BlogsDeployment Forum Community Forums
Community   »   Forums  
Member Login
StandardLiveID


Register
Forgot Password ?

Guests can view and read messages in the community forums, but you must register and log in to Deployment Forum before you can post messages. Click Register at the top of this page. Before posting messages, please read the forum guidelines at the bottom of this page.

Forums > Deployment Solutions > Zero Touch
Subject: ZTI Distribution Shares
Prev Next
You are not authorized to post a reply.

AuthorMessages
warrenddsUser is Offline

Posts:8

Send Message
06/23/2008 8:12 AM  

I've been watching Richards webcasts for using BDD 2007 and SMS 2003 for ZTI, and they have been very helpful (Thanks Richard!). We currently use Windows XP with Office 2003 in our environment, and I need a couple of things clarified:

1. Should I use MDT instead of BDD 2007? If so, what are the differences?

2. It looks as though you need a seperate ZTI share for each deployment because of the settings in Bootstrap.ini. Is this correct?

 

Thanks in advance!

DietmarUser is Offline

Posts:70

Send Message
06/25/2008 2:31 PM  
MDT 2008 supports Windows Vista SP1 and Windows Server 2008. I think that Microsoft integrated a few bug fixes. We deploy different master images for Windows XP SP3 CD-based, Windows XP SP3 with standard software, Windows XP SP2 x64 with standard software with only one ZTI_OSD_SHARE. In this share is the file Bootstrap.ini and the buildid-folders (the buildid is the id of the Task Sequences). The Bootstrap.ini looks like this:

[Settings]
Priority=Model, Default

[Default]
OSDINSTALLSILENT=1
OSDINSTALLPACKAGE=LIZ00326
OSDINSTALLPROGRAM=install

[HP xw8600 Workstation] -- this are our x64 machines
OSDINSTALLSILENT=1
OSDINSTALLPACKAGE=LIZ00327
OSDINSTALLPROGRAM=install

Now copy the file into the buildid-folders. For our CD-based image I set the following:

[Settings]
Priority=Default

[Default]
OSDINSTALLSILENT=1
OSDINSTALLPACKAGE=LIZ00328
OSDINSTALLPROGRAM=install

and copied this file into the buildid-folder of the CD-Based image in ZTI_OSD_SHARE.
In SMS 2003 we made for all different images a OS Image Package. For the OS Image Packages which use the same bootstrap.ini we created one OS Image Installation CD for RIS because they use the same rules in bootstrap.ini. For the CD-based image we made
a separate OS Image Installation CD for RIS because it use different rules in bootstrap.ini. If you change anything in bootstrap.ini don´t forget to copy the new version to the buildid-folders, update the OS Image Package files of all OS Packages and update the distribution points! 

Hope this helps! Dietmar
warrenddsUser is Offline

Posts:8

Send Message
06/30/2008 10:45 AM  

Thanks Dietmar!

But I'm not sure if the way you are using it will work for me. Right now, I'm going to have about 10 different images. (Software deployment is not up yet, so I have to make static images for the time being) Three of them will be:

Windows XP SP3 ACPI

Windows XP SP3 ACPI Uniprocessor

Windows XP SP3 ACPI Multiprocessor

 

The rest will be images built off of the three above, but have different software requirements.

 

We are not using RIS. I will implement WDS though.

If I am understanding you correctly, my Bootstrap.ini file on my ZTI Distribution share should look like this:

[Settings]
Priority=Model, Default

[Default]
OSDINSTALLSILENT=1
OSDINSTALLPACKAGE=Windows XP SP3 ACPI 
OSDINSTALLPROGRAM=Windows XP SP3 ACPI Install


OSDINSTALLSILENT=1
OSDINSTALLPACKAGE=Windows XP SP3 ACPI Uniprocessor 
OSDINSTALLPROGRAM=Windows XP SP3 ACPI Uniprocessor Install

OSDINSTALLSILENT=1
OSDINSTALLPACKAGE=Windows XP SP3 ACPI Multiprocessor
OSDINSTALLPROGRAM=Windows XP SP3 ACPI Multiprocessor Install

 

And my Bootstrap.ini for each of my images should look like this:

[Settings]
Priority=Default

[Default]
OSDINSTALLSILENT=1
OSDINSTALLPACKAGE=WTS0000B
OSDINSTALLPROGRAM=Windows XP SP3 ACPI Install

ResourceRoot=\\%SMSDP%\SMSPKGC$\WTS00004

And:

[Settings]
Priority=Default

[Default]
OSDINSTALLSILENT=1
OSDINSTALLPACKAGE=WTS0000C
OSDINSTALLPROGRAM=Windows XP SP3 ACPI Uniprocessor Install

ResourceRoot=\\%SMSDP%\SMSPKGC$\WTS00004

And:

[Settings]
Priority=Default

[Default]
OSDINSTALLSILENT=1
OSDINSTALLPACKAGE=WTS0000D
OSDINSTALLPROGRAM=Windows XP SP3 ACPI Multiprocessor Install

ResourceRoot=\\%SMSDP%\SMSPKGC$\WTS00004

Does that look right?



 

DietmarUser is Offline

Posts:70

Send Message
06/30/2008 1:54 PM  
Now I am understanding. You use three cd-based images with different software. Once more: If you make your master image on the ACPI-PC you are able to change the HAL during ZTI. Look at this: http://www.myitforum.com/articles/15/view.asp?id=8997 -- This works very fine! We only have 2 master images: one for x86 and one for x64. I made the master image on a Acer TravelMate 290 Notebook and it works on a HP Compaq dc7800, too. :-)) But don´t forget to install the mass storage drivers during sysprep. When you do not work with Modeltypes you don´t need to set Priority=Model, Default -- only Priority=Default. I set ResourceRoot in CS.ini. If you deploy software with SMS you only have a single master image.
You are not authorized to post a reply.
Forums > Deployment Solutions > Zero Touch > ZTI Distribution Shares



ActiveForums 3.7
Forum Policies
Minimize

These forums are a user-supported community for IT professionals to exchange deployment tips, solutions, and techniques. For the benefit of all Deployment Forum members, please observe the following guidelines when posting to these forums:

  • We reserve the right to remove any message. Our moderators will remove all messages that are not respectful or productive. Profanity, racism, prejudice, and flaming are not tolerated.
  • Do not advertise products or services. Our moderators will remove all advertisements or service announcements. Product and service recommendations from active Deployment Forum members are encouraged, however.
  • Make sure your question isn't already answered. Before posting questions, search the forums. After ensuring that your questions are unique, post them to the most appropriate forum. This will help reduce noise in the forums.
  • Help make the most of each thread. Do not post unrelated messages to a thread. Also, if you've resolved a question outside of these forums, please share the solution with other members by posting it back to the thread.
  • Do not share confidential information. Confidential information includes product keys and addresses. Our moderators will edit any message containing confidential information, so double-check messages and their attachments before posting them.
  • Post messages using only the English language. For the benefit of all Deployment Forum members, please post your messages using the English language.

We hope that you enjoy using this community. Please submit your comments and feedback on the Comments and Feedback page or post them to the Comments, Feedback forum.
Privacy Statement  |  Terms Of Use
© 2007 Jerry Honeycutt