Upside

From BluWiki

ENTEO Netinstall 6.0 HOWTO

Logging

Enteo does not really make use of the windows event log. It makes heavy use of its own log directory:

c:\Program Files\Netinstall\nilogs

This is true for both server and client components.

OSD Operating System Deployment

Cache handling

During the first start of the OSD system it looks for free disk space

%CommonFilesDir%\enteo\RepositoryCache

and then reserves space ( default 20% )by creating a dummy file. If this space is eaten up by cached files the tftp server is unable to deliver new files. You see the message "ftp server needs additional time...."

You have to: - shut down OSD services - delete the repository_cache directory - restart osd services

The file structure is recreted and populated with the needed files. Again: 20% of the available space is used ! This can be configured.

PXE 2.0 Setup

If want to setup modern hardware with larger drivers and new network cards you beed to switch to PXE20:

Install Windows Automated Installation Kit (AIK) [1]

Then run makewim.vbs out of

%NI_DIR%\OSDeployment\OSD\....\Tools

To add additional drivers to the boot set copy them into the drivers dirctory ( no subfolders ). You can see them beeing inserted if you turn on the debug switch during WIM creation.

These drivers are used during the first three stages of the setup:

• Partitioning
• Formating
• Copying of OS files

As WAIK is based on VISTA technology I had to insert vista drivers here not XP ( for example Intel SATA driver ).

PXE20 has some problems partitioning hard discs. If you create partitions larger than 4 GB you might get into problems.

Messages like: No operating system etc. ( no bluescreen ) This is not a driver problem. It is a problem of the bios not beeing able to load the os. ( seen on Dell Optiplex 755, Intel SATA Chipset )

Here you can read details: Troubleshooting Disks and Partitioning [2]

There is two ways to solve the problem:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vds\Alignment]
@="Alignment Settings in Bytes"
"Between4_8GB" =dword:0
"Between8_32GB" =dword:0
"GreaterThan32GB" =dword:0
"LessThan4GB" =dword:0

To change the registry of your pe20.wim file you have to

• create empty dir c:\mount
• imagex /mountrw C:\enteo\pxe20.wim 1 c:\mount
• reg load HKLM\PE-SYS c:\mount\Windows\system32\config\system
• Reg Add "HKLM\PE-SYS\ControlSet001\Services\vds\Alignment" /t Reg_Dword /v LessThan4GB /d 0 /f
• Reg Add "HKLM\PE-SYS\ControlSet001\Services\vds\Alignment" /t Reg_Dword /v Between4_8GB /d 0 /f
• Reg Add "HKLM\PE-SYS\ControlSet001\Services\vds\Alignment" /t Reg_Dword /v Between8_32GB /d 0 /f
• Reg Add "HKLM\PE-SYS\ControlSet001\Services\vds\Alignment" /t Reg_Dword /v GreaterThan32GB /d 0 /f
• reg unload HKLM\PE-SYS
• imagex /commit /unmount c:\mount

http://msdn2.microsoft.com/en-us/lib...u84rl10kephll5
http://www.msfn.org/board/lofiversion/index.php/t88083.html

Or you can add these commands to your boot script.

Diskpart

select disk 0
clean
create partition primary align=16065
assign letter=c:
active
exit

Driver integration

If you need to add drivers for a hard disc or a network card you have to add them twice:

• you have to integrate them into you pe wim. See above ( Vista drivers )
• you have to integrate them in your os that is to be installed ( OS dependent )

For the drivers of the second type you have to create a driver package. This package has to be assigned to the "New Comuters" container. Don't worry about the "0 instances created" message. The instances are dynamically vreated during the run of Windows PE.

The PEInit application scnas for all devices and tries to find the matching drivers.

• It compares to Vendor ID
• It compares the OS type.

If you select the driver package in the software folder you can see the enabled operating systems on ther properties pane on the right side. When the operting system being installed starts for the first time the dynamically created driver instance must be visible on the "Drivers" tab of the computer. If it is not visible check the criteria above.

The dynamic creation of driver instances can be seen in the "blsclient_webservice.log" logfiles. By changing the following paramrter of the "web.config" in c:\Inetpub\MgntPoint\blsClientManagement.

<logger name= "Enteo.BlServer.PolicyInstanceManagement">
<level value="DEBUG" />
</logger>

Additional information ( in german ) [3]