Re: SMS RIS and OSD

Follow these instructions:
==================

Installing and Configuring RIS 2003

Installing RIS on Windows Server 2003
1. From Windows 2003 Server, on the Start menu, select Settings, and then
click Control Panel.
2. Double-click Add/Remove Programs.
3. Click Add/Remove Windows Components button at the bottom-left.
4. Scroll down, check the Remote Installation Services box, and then click
Next.
5. Enter the path for the Windows 2003 CD source files when prompted.
6. Click Finish to exit the wizard.
7. When you are prompted to restart your computer, click Yes.
8. When the server has restarted, log on to the computer as an administrator
with Enterprise Administrator privileges.

Configuring RIS for OS Deployment
1. On the RIS server, map a network drive to the location of the Windows XP
Professional with Service Pack 2 source files. If you already have the CD,
this would be OK as well.
2. On the Start menu, select Run, and enter the command risetup.exe and
press Enter to start the Remote Installation Services Setup Wizard. When the
Welcome page displays, click Next.
3. On the Remote Installation Folder Location page, enter the drive letter
and path to where you want the RIS installation folder created in the Path
text box, and then click Next. The drive letter is most likely D: on your
secondary site servers.
4. On the Initial Settings page, enable the Respond to client computers
requesting service option, and then click Next.
5. On the Installation Source Files Location page, enter the path to the
Windows XP Service Pack 2 source files, and then click Next.
6. On the Windows Installation Image Folder Name page, enter wpe.2k5.prod,
and then click Next. Make sure to include the “.” (period) in the folder
name.

Note wpe.2k5.prod = <OS platform>.<version>.<environment>

7. On the Friendly Description and Help Text page, type something to
identify the install, and for the help section, type Uses Windows
Preinstallation Environment (PE) to launch the Business Desktop Deployment
(BDD) process.
8. Click Next to continue.
9. On the Review Settings page, review and verify your selections. If you
need to make changes, use the Back button to return to previous pages. Click
Finish to continue.
10. When the installation is complete, click Done.


Authorizing the PXE portion of RIS in Active Directory
NOTE: You will need to be an Enterprise Admin to authorize a RIS server in
Active Directory.

1. On the DHCP server, navigate to the Administrative Tools program group
and select DHCP to run the DHCP snap-in. The DHCP snap-in is unavailable on
the RIS server.
2. Right-click DHCP in the upper-left corner of the DHCP snap-in, and then
select Manage Authorized Servers. If the RIS server is not already listed,
click the Authorize button and then enter the IP address of the RIS server.
Click Yes when you are prompted to verify that the address is correct.

Configuring RIS to generate a random computername
You must configure RIS to generate a random computername so that each
computer you install, is uniquely identified on the network when booting.

Use a Notepad to open the file
<drive-letter>:\RemoteInstall\Setup\English\Images\wpe.2k5.prod\i386\templates\ristndrd.sif.

Search for the line:
ComputerName = %MACHINENAME%

Modify this line by changing %MACHINENAME% TO RIS%MAC%
ComputerName = RIS%MAC%


What this modification does is use the MAC Address of the first nic on the
target machine and then adds the letters “RIS” as a prefix. For example:
ComputerName = RIS00CA8FB47D03

By using the MAC address of the first nic on the target machine as part of
the computername, this guarantees the uniqueness of the computer on the
network when booting under RIS.

Configuring RIS to boot to minint (WinPE)
You must configure each operating system you are deploying with RIS to boot
to minint by modifying the file ristndrd.sif.

Use Notepad to open the file
<drive-letter>:\RemoteInstall\Setup\English\Images\wpe.2k5.prod\i386\templates\ristndrd.sif.

Search for the line:
OsLoadOptions = "/noguiboot /fastdetect"

Modify this line by adding the command option /minint as follows:
OsLoadOptions = "/noguiboot /fastdetect /minint"


Disable Creation of Windows PE Computer Accounts in Active Directory
During the OS deployment process, Windows PE will create a computer account
in Active Directory by default. The computer name that Windows PE uses is
temporary and unnecessary after Windows PE has prepared the workstation for
Windows XP deployment.
To modify the Ristnrd.sif file to disable the creation of computer accounts
in Active Directory, perform the following steps:

In Notepad, open
<drive-letter>:\RemoteInstall\Setup\English\Images\wpe.2k5.prod\i386\templates\Ristndrd.sif.

Modify the ImageType entry in the [OSChooser] section to ImageType=WinPE

[OSChooser]
Description ="My BDD Windows XP SP2 Deployment"
Help ="Uses Windows Preinstallation Environment (PE) to launch the Business
Desktop Deployment (BDD) process"
LaunchFile = "%INSTALLPATH%\%MACHINETYPE%\templates\startrom.com"
ImageType =Flat
Version="5.1 (0)"

After modification, the [OSChooser] section should resemble the text below

[OSChooser]
Description ="My BDD Windows XP SP2 Deployment"
Help ="Uses Windows Preinstallation Environment (PE) to launch the Business
Desktop Deployment (BDD) process"
LaunchFile = "%INSTALLPATH%\%MACHINETYPE%\templates\startrom.com"
ImageType =WinPE
Version="5.1 (0)"

Save the file, and then close Notepad.

Create Operating System Image Installation CD
For RIS to deploy out an OS Image Package, SMS must currently have the OS
Image Package created and configured. You must also create an Operating
System Installation CD to be incorporated into the RIS boot image. The
following instructions detail how to create the OS Image Installation CD and
integrate the installation CD into RIS.


1. Open the SMS Administrator Console
2. Expand the SMS Site Database
3. Highlight Image Package node
4. Right-click, choose All Tasks, then choose Create Operating Installation CD
5. Click Next on the Welcome to the Operating System Image Installation CD
Wizard screen.
6. On the Installation settings screen, select all available choices with
the exception of the last “Automatically choose the Operating System Package
to install by running a custom program or script”. Make sure this one is
NOT checked.
7. Click Next.
8. IMPORTANT Before continuing with this step, you must first make sure the
secondary site is added as a distribution point for the package(s) and then
select the specific site-server/location as the distribution point for the CD
you are creating. This assures when RIS is used to deploy “fresh”
installations at that particular location, the image will be deployed from
that particular location’s secondary site server and not anywhere else.

A good practice to follow in configuring a secondary site server (eg. a
plant server) as a distribution point for the package, is to make sure you
add the site server to the list of distribution points about 2 days in
advance before using that site server to deploy “fresh” install images to
clients. This will allow time for necessary file copying, replication and
configuration updates.

On the Install from SMS distribution points screen, select the image and
choose the SMS site to handle request for distribution points. (This should
be the primary site server). Click Next.

9. On the Windows PE settings screen, add any additional drivers needed to
the Installation CD. Click Next.

Note The path to the additional drivers is: \\<primary site
server>\Unattend\Boot Disks\WINPE\Extranics

10. On the Create CD image screen, provide a name for the Installation CD as
well as the path to a file name ending in iso. Click Next.
11. Click Finish on the CD Creation Complete screen.
12. Copy the newly created ISO file, to the computer where you will be able
to burn a CD from the ISO
13. Follow your CD-burning software’s instructions to burn a CD of the new ISO


Copy Windows PE boot-files to the RIS Server
So that the target computer is able to boot into Windows PE, as opposed to
Windows XP Professional, you need to copy the Windows PE boot-files from the
OS Image Installation CD to the RIS server.

1. First, delete the following files from <drive-letter on RIS
server>:\remoteinstall\setup\english\images\wpe.2k5.prod\i386\templates
folder on the RIS server.:

• Ntdetect.com
• ntldr

2. Copy the following files from the OS Installation CD <CD-drive>:\i386 to
<dirve-letter on RIS
server>:\remoteinstall\setup\english\images\wpe.2k5.prod\i386\templates:

• Ntdetect.com
• Setupldr.exe (rename to NTLDR after copying)



Copy Image Installation CD files to the RIS Server
Copy the following folders on the OS Image Installation CD to the root
directory of <dirve-letter on RIS
server>:\remoteinstall\setup\english\images\wpe.2k5.prod\ folder on the RIS
server.

• <OS Installation CD>:\I386
• <OS Installation CD>:\Program Files

Note During the copy, if you are prompted to overwrite existing files,
click Yes or Yes to all

Copying network driver files to the root of I386 directory
1. After copying folders, go to: <drive-letter on RIS
server>:\remoteinstall\setup\english\images\wpe.2k5.prod\I386\System32
2. Select/highlight all nic driver files by pressing the Ctrl-key and
simultaneously clicking each file in the list below until ALL of them are
selected/highlighted:
• b57win32.cat
• b57win32.inf
• b57xp.sys
• e100b325.cat
• e100b325.inf
• e100b325.sys
• E100NT5.SYS (select if it exists)
• e1000b325.cat (Gigabit driver)
• e1000b325.inf (Gigabit driver)
• e1000b325.sys (Gigabit driver)
• E1000NT5.SYS (select if it exists)

3. Copy the highlighted files to root of <drive-letter on RIS
server>:\remoteinstall\setup\english\images\wpe.2k5.prod\I386

Note During the copy, if you are prompted to overwrite existing files,
click Yes or Yes to all

4. Delete the following files if they following files at <drive-letter on
RIS server>:\remoteinstall\setup\english\images\wpe.2k5.prod\I386:
• b57xp.PNF (if it exists)
• b57win32.PNF
• e100b325.PNF
• e1000b325.PNF
• e100NT5.PNF
• e1000b325.PNF

You must now restart the RIS service on the RIS server (do NOT reboot the
server, it’s not necessary). To stop and restart the RIS service, open a
command prompt on the RIS server and type the following commands:
net stop binlsvc
net start binlsvc


Disabling Windows PE Logging on the RIS Server
By default, Windows PE writes startup information to the Setupapi.log log
file. When several workstations simultaneously boot the same Windows PE
image, those workstations attempt to write to the same Setupapi.log file,
which can cause slow performance because each workstation must wait to gain
write access to the file. In the OS Deployment process, RIS status logging is
not required for Windows PE.

To disable Windows PE logging on the RIS server, perform the following steps:
Modify the registry settings in the Windows PE image on the RIS server.
Set read-only access on the Setupapi.log file in the Windows PE image on the
RIS server.

Modify the Registry Settings in the Windows PE Image
To modify the registry settings in the Windows PE image on the RIS server,
perform the following steps:
1. On the RIS server, click Start, click Run, and then type RegEdt32.exe in
the Open text box.
2. Click the HKEY_LOCAL_MACHINE registry subtree.
3. On the File menu, click Load Hive.
4. Navigate to <drive-letter on RIS
server>:\remoteinstall\setup\english\images\wpe.2k5.prod\I386\System32\Config, click Software, and then click Open.
5. In the Key Name text box, type TemporaryHiveName (where TemporaryHiveName
is a temporary name you assign to the hive), and then click OK.
6. In the Registry Editor, navigate to
TemporaryHiveName\Microsoft\Windows\Currentversion\Setup (where
TemporaryHiveName is a temporary name you assign to the hive).

For example:
My Computer ->HKEY_LOCAL_MACHINE -> TEMPHIVE -> Microsoft -> Windows ->
CurrentVersion -> Setup

7. On the Edit menu, click New, and then click DWORD Value.
8. For the name of the new value, type LogLevel, and then press ENTER.
9. Double-click LogLevel, select Hexadecimal in Value data type 101, and
then click OK.
10. Verify that the LogLevel entry now has a value of 0x00000101.
11. Click My Computer ->HKEY_LOCAL_MACHINE -> TEMPHIVE.
12. On the File menu, click Unload Hive.
13. In the Unload Hive dialog box, click Yes.
14. Close the Registry Editor.


Set the Setupapi.log File to Read-only
To set the Setupapi.log file to read-only, perform the following steps:

Note In the steps below, you will be searching for Setupapi.log. If
Setupapi.log does not exist, then create it manually by right-clicking an
empty area inside the i386 folder and select New | Text Document. After the
file is created, rename it to Setupapi.log and continue with the steps below.

1. Open Windows Explorer and navigate to <drive-letter on RIS
server>:\remoteinstall\setup\english\images\wpe.2k5.prod\I386
2. In the details pane, right-click Setupapi.log, and then click Properties.
3. In the Setupapi.log Properties dialog box, select Read-only, and then
click OK.
4. Close Windows Explorer.

Enabling Only Tools in the Choice Options Dialog Box
To enable the Tools (Maintenance and Troubleshooting) option in the Client
Installation Wizard, perform the following steps:
1. Logon to the domain the RIS server is in as an administrator and start
Active Directory Users and Computers.
2. In the console tree, browse to GroupPolicyContainer (where
GroupPolicyContainer is either the domain or the organizational unit (OU)
that contains the RIS servers), right-click GroupPolicyContainer, and then
click Properties.

Note: This step assumes that the Default Domain Policy object has been
propogated/recursed and enforced starting from the top-level of the Active
Directory domain that the RIS server(s) belong to. Also, you MUST use the
Default Domain Policy object for this. If you do not use this GPO, the
Choice Options you attempt to disable below, will still be visible when you
connect to the RIS server.

Note If you do not know what organizational unit (OU) the RIS servers are
in, get with your Active Directory system administrators for further details

3. On the Group Policy tab, click the default domain policy, and then click
it.
4. In the console tree of the Group Policy Object Editor, expand User
Configuration, expand Windows Settings, and then click Remote Installation
Services.
5. In the details pane, double-click Choice Options.
6. In the Tools section of the Choice Options Properties dialog box, click
Enabled.
7. In the Automatic Setup section, click Disabled.
8. In the Custom Setup section, click Disabled.
9. In the Restart Setup section, click Disabled, and then click OK.
10. Close the Group Policy Object Editor.
11. Close Active Directory Users and Computers.


"Per Elmsäter" wrote:

Thanks again Troy for your hands on instructions. It was easy as pie
following them.

However, nothing happened as to my problems. Seems I've done some basic
mistake earlier on in the chain. The documenation is really fragmented as to
how to deploy this OSD created Image.

I've created an Installation CD from OSD in SMS using an Image Package that
works flawlessly when distributing it via SMS.
I've extracted and burnt the image to a CD.
I've copied the contents of the CD to a Folder under the
\\risserver\Reminst\setup\Swedish\Images\MyOSDImageFolder
Not the iso file but an extracted tree structure.

At this point still no meny Item is enumerated and I cannot choose this
Image. I have three other Images in the same parental path and they can be
found. They've been created with rissetup.exe and there is a \i386\templates
folder with the file ristndrd.sif. If I copy this folder into my OSD Image I
get it enumerated on the meny but it doesn't work.
If I create an Image with rissetup and then copy my OSD Image on top of this
I get a meny enumeration but it still doesn't work.

After choosing my menyitem I get a black screen with this text at the bottom
Starting Windows Preinstallation Environment
and a progress bar.

When the progress bar is done the screen goes black and all there is is a
blinking cursor.

Alternately.
If I try to install from the CD that was created I get one step more. After
the previous message is displayed the WinPE install bitmap with the
mountains comes up and the message initializing WinPe Sometimes a couple of
commandprompts are run like osdenv.exe I believe. When the machine reeboots
after initialization it will bypass the installation and boot straight back
to the old OS that was previously installed.

I tried pressing shift + several function keys until I get an Errormessage
popupbox . This box remains empty.

~Confused
Per Elmsäter


"Troy L. Martin" <TroyLMartin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D3F9B788-4C20-4A92-8B4E-1F747ED23749@xxxxxxxxxxxxxxxx
WPE w/ RIS runs under the "Tools" RIS Choice Options. Follow these
instructions to test:

Open ADUC for the domain your RIS server is in

View the properties for the OU your RIS server is in

On the Group Policy tab, click the default domain policy, and then click
it.

In the console tree of the Group Policy Object Editor, expand User
Configuration, expand Windows Settings, and then click Remote Installation
Services.

In the details pane, double-click Choice Options.

In the Tools section of the Choice Options Properties dialog box, click
Enabled.

In the Automatic Setup section, click Disabled.

In the Custom Setup section, click Disabled.

In the Restart Setup section, click Disabled, and then click OK.

Close the Group Policy Object Editor.

"Per Elmsäter" wrote:

Is it not possible to have the standard flat images on the RIS server
when
deploying OS Images created with OSD in SMS2003 Server?

I already have flat Images on a RIS server that installs the OS.
I have set up an SMS server and created Image Packages with OSD USMT and
ZTI. From this Image Package I have created an "Operaing System Image
Installation CD" I've unpacked the iso file on the RIS server. Ie in the
Images file structure alongside with the old flat OS Images.

My first prooblem is that RIS does not Enum this Image in the Oscoice.osc
file. I cannot find any information on how to make it available for the
list
that populates this menu.
The only information I find is how to bypass user interaction in
Welcome.osc
and Login.osc. At this point I still want user interaction. Is this not
possible to achieve?
In another note I am instructed to tell the OS to boot from Minint

Use a text editor to open the file
\RemoteInstall\Setup\English\Images\3486\i386\templates\ristndrd.sif.
Search
for the line:

OsLoadOptions = "/noguiboot /fastdetect"

Modify this line by adding the command option /minint as follows:

OsLoadOptions = "/noguiboot /fastdetect /minint"


This file path does not exist on my Reminst share. I don't have an
English
but a Swedish path. Evenso there is no 3486 folder nor a templates folder
in
my i386 folder. Nor a .sif file anywhere that has the OsLoadOptions
argument
to modify.

I'd mucjh appreciate if anybody can clue me in on how to sew this all up.

Thanks.
Per Elmsäter






.

Loading