Quantcast
Channel: Ivanti User Community : All Content - OS Deployment and Provisioning
Viewing all articles
Browse latest Browse all 1803

How to pre-stage the PXE representative deployment for slow networks or network with low bandwidth

$
0
0



Reviewed: November 2014

 

Versions Effected: LDMS 9.5

 

Problem/ Scenario:

You have a office on the other side of the world/ continent that you need to deploy a PXE representative to so that you can either imaging your machines using provisioning or continue to do so. The connection between the core and the target PXE representative is very slow and the machine is always in use. I.e you have decided to use your file server or DC in the office.

 

Solution:

I have created a two part script attached to this case ready for import. To split the PXE Representative deployment process into two parts.

1. Copy over all the files required for the PXE representative and associated services.

 

2. Install the PXE representative , registering services using the files on that machine.

Files for the PXE Representative

Services used within the process

 

Further Details:

I have edited the current PXE Deployment script and split the process in two. One script to copy over the required files and the second script to run the msi to install the PXE rep and additional services.
These scripts are attached to the case as :
Pre-Stage- PXE Deployment Stage 1
Pre-Stage- PXE Deployment Stage 2

 

Import the scripts into the Manage Scripts module of the Distribution component

 

Run the stage 1 script to copy the files over and the stage 2 script to install the PXE services and application.


Scripts:

We at LANDESK understand how our customer operate and the different security precautions in place for the many different environments that our product is located within. With that in mind I have posted the scripts here as well so if you cannot download them because of secruity blocks then you can either cut and past them or type them out a fresh. In sense copying the procedure above.


To create the scripts manually follow these steps:

Within the 'Distribution' component under manage scripts. (Optional Create a new folder to allow for easy administration and scheduling of the scripts)

Right click in the manage scripts window and click 'New Custom Script' to create the script itself:

Highlight all the default text and remove it so you are left with a blank canvas.

Copy and paste or type out a fresh the script below :

:Pre-Stage- PXE Deployment Stage 1
[MACHINES_NT]

REMEXEC0=MsiExec.exe /x {F238CE99-6614-4072-9D20-1D2FA7ED951A} /q

;{These files installed by OSDRep.msi in the older version
REMCOPY1=%DTMDIR%\landesk\files\bootmenu.1, %LDMS_CLIENT_DIR%\bootmenu.1, TOREMOTE
REMCOPY2=%DTMDIR%\landesk\files\bstrap.0, %LDMS_CLIENT_DIR%\bstrap.0, TOREMOTE
REMCOPY3=%DTMDIR%\landesk\files\dosundi.1, %LDMS_CLIENT_DIR%\dosundi.1, TOREMOTE
REMCOPY4=%DTMDIR%\landesk\vboot\bootmenu.0, %LDMS_CLIENT_DIR%\bootmenu.0, TOREMOTE
REMCOPY5=%DTMDIR%\landesk\vboot\dosundi.0, %LDMS_CLIENT_DIR%\dosundi.0, TOREMOTE
;}

;{These files are needed by winpe2.0 and later
REMCOPY6=%DTMDIR%\landesk\vboot\bcd.dat, %LDMS_CLIENT_DIR%\bcd, TOREMOTE
REMCOPY7=%DTMDIR%\landesk\vboot\bcd_x64.dat, %LDMS_CLIENT_DIR%\bcd_x64, TOREMOTE
REMCOPY8=%DTMDIR%\landesk\vboot\bcd_ia32.dat, %LDMS_CLIENT_DIR%\bcd_ia32, TOREMOTE
REMCOPY9=%DTMDIR%\landesk\vboot\boot.sdi, %LDMS_CLIENT_DIR%\boot.sdi, TOREMOTE
REMCOPY10=%DTMDIR%\landesk\vboot\boot.wim, %LDMS_CLIENT_DIR%\boot.wim, TOREMOTE
REMCOPY11=%DTMDIR%\landesk\vboot\boot_x64.wim, %LDMS_CLIENT_DIR%\boot_x64.wim, TOREMOTE
REMCOPY12=%DTMDIR%\landesk\vboot\bootx64.efi, %LDMS_CLIENT_DIR%\bootx64.0, TOREMOTE
REMCOPY13=%DTMDIR%\landesk\vboot\bootia32.efi, %LDMS_CLIENT_DIR%\bootia32.0, TOREMOTE
REMCOPY14=%DTMDIR%\landesk\vboot\bootmgr.exe, %LDMS_CLIENT_DIR%\bootmgr.exe, TOREMOTE
REMCOPY15=%DTMDIR%\landesk\vboot\pxeboot.0, %LDMS_CLIENT_DIR%\startrom.0, TOREMOTE
;}

REMCOPY16=%DTMDIR%\landesk\files\osdrep.msi, %LDMS_CLIENT_DIR%\osdrep.msi, TOREMOTE

[MACHINES_95]
SETSTATUS=1240, ERR

[OWNER]
TYPE=OSDOTHERS




Save and rename as Pre-Stage- PXE Deployment Stage 1

 

Create a second script following the method above and enter the following text:

:Pre-Stage- PXE Deployment Stage 2
[MACHINES_NT]
REMEXEC0=MsiExec.exe /x {F238CE99-6614-4072-9D20-1D2FA7ED951A} /q
REMEXEC1=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /p="http://%CUSTJOBHOSTIP%/landesk/files/osdrep.msi" /msi /N /An /Ac /g="{F238CE99-6614-4072-9D20-1D2FA7ED951A}" /disableclientqueue
REMEXEC2=<qt/>%LDMS_CLIENT_DIR%\LDISCN32.EXE<qt/> /NTT=%CUSTJOBHOSTIP%:5007 /S="%CUSTJOBHOSTIP%" /F /SYNC /NOUI

[MACHINES_95]
SETSTATUS=1240, ERR

[OWNER]
TYPE=OSDOTHERS




Save and rename as Pre-Stage- PXE Deployment Stage 2


Note: If you know of ways in which we can improve this script, let me know and I will update the article with the latest versions. After verifying them in my lab.


Viewing all articles
Browse latest Browse all 1803

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>