Deployment and Imaging Group

 View Only
Back to Library

How to Customize WinPE 4.x in Altiris 7.5 

Mar 06, 2014 02:41 PM

##########################################################################################################

This is NOT supported by Symantec, so remember to back up the files, case you want to revert back.

##########################################################################################################

How to modified WinPE 4.x in Altiris 7.5 HF4

In this article, you'll learn, 

  • How to add tools and utilities into WinPE x86 (since most of these tools are not available in x64)
    • VNC
    • RocketDock
    • Sysinternals Tools
    • Unix Utilities
    • Notepad
    • Regedit
    • BGInfo
    • Q-Dir (WinPE version of explorer)
  • How to add WinPE optional packages, like: PowerShell, .Net, etc.
  • How to change WinPE background picture
  • Display the Symantec GUID, Computer Serial Number (Dell since that is what we use) in the BGINFO
     

*All the files I use in my environment will be included in the end

 

My WinPE Environment:

On our WinPE environment we decide to implement extra tools to help us troubleshooting problems during the WinPE. Also we added extra information on the background (BGInfo) so is easy for our tech guys on the field to identify a computer when deploying to a lab with 100+ computers. Normally when is manage this is not a problem, but for new computers and replace computers, where Altiris uses the minint name (in 7.5 serial) helps identify and send tasks.

After trying different configurations we settle for the configuration show on the picture below. We display general computer information, plus serial number, minint name and Altiris GUID number.

Also we have the Microsoft components running like PowerShell and .Net added to the WinPE environment and for remote connections we decide to use VNC for now.

WinPE.jpg

 

Important File Locations to Know:

The Folders and Files locations below is assuming the PXE server is install on a speared server (so not on the NS). Since I don’t have an environment where the PXE and NS are in the same server, I can’t tell info the location below will change. So make sure you keep that into consideration.

[Altiris Install Dir] - assuming it is on default locations [C:\Program Files\Altiris]

 

  • On the Notification Server - (these will be the files you need to modified)
  • Location of the WinPE Background Picture: [winpe.bmp] and [winpe.jpg]
  • [Altiris Install Dir]\Deployment\BDC\bootwiz\Platforms\WinPE\x86\Optional\Boot
     
  • Location to add the utilities and tools:
  • [Altiris Install Dir]\Deployment\BDC\bootwiz\oem\DS\winpe\x86\Base
     
  • Location of the [WINPE.WIM] file:
  • [Altiris Install Dir]\Deployment\BDC\WAIK\Tools\PETools\x86
     
  • Location of Automation Files:
  • [Altiris Install Dir]\Notification Server\NSCap\bin\Win32\X86\Deployment\Automation\PEinstall_x86
     
  • On the Site Server (PXE) - (files below get overwrite every time you re-build the WinPE environment, from the package server)
  • Location of the WinPE Background Picture: [winpe.bmp] and [winpe.jpg]
  • [Altiris Install Dir]\Altiris Agent\Agents\Deployment\SBS\Bootwiz\{GUID}\cache\bootwiz\Platforms\WinPE\x86\Optional\Boot
     
  • Location to add the utilities and tools:
  • [Altiris Install Dir]\Altiris Agent\Agents\Deployment\SBS\Bootwiz\{GUID}\cache\bootwiz\oem\DS\winpe\x86\Base
     
  • Location of the [WINPE.WIM] file:
  • [Altiris Install Dir]\Altiris Agent\Agents\Deployment\SBS\Bootwiz\{GUID}\cache\WAIK\Tools\PETools\x86

 

Geting ready for the WinPE customizations:

Before starting the customization, make sure you have done the following steps:

  1. Download the attached files from this article "WinPETools.zip"
  2. Read the notes on the bottom of the article that explains what the files (scripts) do, case you would like to add or remove extra tools and functionality
  3. Have access to your NS, Package and PXE server
  4. Have a reference computer ready, since you will need to install ADK, and you don’t want do that on the server
    a. Install the Windows Assessment and Deployment Kit (ADK) for Windows 8 (which is WinPE 4.0) on a reference computer to add the extra components into WinPE, instructions for the process is on section “Adding PE Optional Components Ref into WinPE”
    b. To download ADK: http://www.microsoft.com/en-us/download/details.aspx?id=30652
  5. If you decide to use VNC as a remote option, on “Adding Tools to the WinPE” have the KB link explain the process. But if you decide not to used, than you need to do the following:
    a. Delete the files: ultravnc.ini, winvnc.exe, vnchooks.dll
    b. Delete or comment the following lines 19 and 20 from the file “WKU_WinPE.bat”
        i.  echo Launching VNC server...
        ii. start x:\Utilities\winvnc.exe

 

So let's get started:

Once the pre-configurations above are in place, there are only 3 steps:

  • Adding PE components
  • Adding the Extra Tools, like BGIngo, RocketDock, etc
  • Build the WinPE environment

 

Adding PE Optional Components Reference into WinPE:

I noticed that after build a standard WinPE using the Altiris tools, that components like PowerShell and .Net was not enable by default, this present a problem if you are trying to use scripts in PowerShell or .Net. One of the problems I found it was that if you run the powershell script from the console. It will display it was run successfully. Like the picture below:

powershell.jpg

But after looking at the details of the job, I noticed the output properties display the powershell.exe is missing or not install. So the script never run. Since we use powershell scripts and .Net tools, I decided to add the extra components into WinPE and below are the steps to do it.

For more information in building and modifying the WinPE environment, go to the following links:

There is 2 files inside the .ZIP attached to this article:

Before running the batch script “WinPESettings.bat” you will need:

  • Make sure ADK is installed
     
  • Create the following structure on the reference computer root
    • C:\WinPEx86
    • C:\WinPEx86\mount
       
  • Copy the file “WINPE.WIM” from the notification server to “C:\WinPEx86”.
    • NS File location: [Altiris Install Dir]\Deployment\BDC\WAIK\Tools\PETools\x86 - for the x86 WINPE.WIM.
       
  • Copy the “WinPESettings.bat” to the reference computer root
     
  • Browse to > Start > All Programs > Windows Kits > Windows ADK
    • Run: Deployment and Imaging Tools Environment
    • This will open a CMD with the right environment variables set, just go back to the root and run the WinPESettings.bat file from the open CMD
       
  • If you decide to added the “unattend.xml” to set the resolution than, you will need to comment out lines 78, 79 and 80 from the “WinPESettings.bat”, once the batch file added all the components you need to copy the unattend.xml to the following locations:
    • C:\WinPEx86\mount
    • C:\WinPEx86\mount\Windows\System32
    • once you added the xml file
    • unmount the WINPE.WIM image by running the following command on the open CMD
    • Dism /Unmount-Image /MountDir:"C:\WinPEx86\mount" /commit

Once you are done with the WINPE.WIM file, than you will need to move the file back to the Notification Server.

 

Just a sample of the batch file, full code is attached to this article:

ECHO ***********************************************************
ECHO ** Mount Windows PE boot image "winpe.wim"               **
ECHO ***********************************************************
imagex /mountrw c:\winpex86\winpe.wim 1 c:\winpex86\mount

ECHO ** Adding Package [WinPE-WMI]                            **
DISM /Add-Package /Image:"C:\WinPEx86\mount" /PackagePath:"[path to Windows Kits]\x86\WinPE_OCs\WinPE-WMI.cab"

ECHO ** Adding Package [WinPE-NetFx4]                         **
DISM /Add-Package /Image:"C:\WinPEx86\mount" /PackagePath:"[path to Windows Kits]\x86\WinPE_OCs\WinPE-NetFx4.cab"

ECHO ** Adding Package [WinPE-Scripting]
DISM /Add-Package /Image:"C:\WinPEx86\mount" /PackagePath:"[path to Windows Kits]\x86\WinPE_OCs\WinPE-Scripting.cab"

ECHO ** Adding Package [WinPE-PowerShell3]                    **
DISM /Add-Package /Image:"C:\WinPEx86\mount" /PackagePath:"[path to Windows Kits]\x86\WinPE_OCs\WinPE-PowerShell3.cab"

ECHO ** Adding Package [WinPE-MDAC]                           **
DISM /Add-Package /Image:"C:\WinPEx86\mount" /PackagePath:" [path to Windows Kits]\x86\WinPE_OCs\WinPE-MDAC.cab"

ECHO ** Adding Package [WinPE-HTA]                            **
DISM /Add-Package /Image:"C:\WinPEx86\mount" /PackagePath:" [path to Windows Kits]\x86\WinPE_OCs\WinPE-HTA.cab"

ECHO ** Adding Package [WinPE-DismCmdlets]                    **
DISM /Add-Package /Image:"C:\WinPEx86\mount" /PackagePath:" [path to Windows Kits]\x86\WinPE_OCs\WinPE-DismCmdlets.cab"

ECHO ***********************************************************
ECHO ** Unmount the Windows PE Image                          **
ECHO ***********************************************************
Dism /Unmount-Image /MountDir:"C:\WinPEx86\mount" /commit

 

Adding Tools into WinPE

These part you will prepare the environment with all the files, so the system will be ready to build the WinPE.

Download the WinPETools.zip from the article and make sure you have all your settings ready.

For VNC, there are other articles out there that explain the process (http://www.symantec.com/connect/articles/winpe-21-remote-control-ultravnc), this one is not necessary for 7.1 or 7.5, but the process is very similar, the major difference is that VNC change the settings location from registry to INI file. All the VNC files are include on the download, all you need to do is build the ultravnc.ini I am including the file but I erase the password field.

Getting all files setup:

  • Login to the NS
    • Make sure you back up the originals Files, case you want to revert back.

 

  • Extract the “WinPETools.zip”
     
  • Copy folder “Utilities” > [Altiris Install Dir]\Deployment\BDC\bootwiz\oem\DS\winpe\x86\Base
    • While you are on the “[Altiris Install Dir]\Deployment\BDC\bootwiz\oem\DS\winpe\x86\Base” folder
    • Edit the file “runagent.bat”
    • Add the following command on the bottom of the batch file

 

REM Set PowerShell to unrestricted
ECHO Starting PowerShell
IF EXIST x:\Windows\System32\WindowsPowerShell\v1.0\PowerShell.exe x:\Windows\System32\WindowsPowerShell\v1.0\PowerShell.exe Set-ExecutionPolicy Unrestricted

 

  • This will initialize the custom script to start rocketdock, bginfo, etc …
REM Start Utilities
ECHO Start Utilities
IF EXIST x:\Utilities\WKU_WinPE.bat x:\Utilities\WKU_WinPE.bat

 

  • Copy background pictures > [Altiris Install Dir]\Deployment\BDC\bootwiz\Platforms\WinPE\x86\Optional\Boot
    • I didn’t add the background picture, since it is customize for my environment, but you just need to create one and replace the files on the folder above
       
  • Replace the modified “WINPE.WIM” > [Altiris Install Dir]\Deployment\BDC\WAIK\Tools\PETools\x86

 

Process to build the WinPE files on a PXE Site Server

Since in our environment we don’t have the PXE services running on the NS, we assign a site server as our PXE server.

So the process to get your custom files inserted into the WinPE environment is:

  1. Add all the customizations files/settings on the locations show above (Notification Server)
  2. In 7.5 the BootWiz folder is itself, part of a package, so normal package replication will pick up the changes, though it could take up to 24 hrs to update site servers. You can either wait or force the replication by running the Scheduler task:
    1. Run taskschd.msc
      1. Click [Task Scheduler Library]
      2. Right-click > run the following tasks
    2. NS.Package Distribution Point Update
    3. NS.Package Refresh
    4. NS.Delta Resource Membership Update
  3. Once the replication tasks runs, go to the package server to make sure the following package was update:
    bcd_pck.jpg
  4. Once the package is update on the Site Server [Package]
    1. Go to the Altiris Console > Settings > All Settings > Deployment and Migration > Preboot Configurations
    2. Click on the WinPE environment you would like to re-create and click the button [Recreate Preboot Environment
      preboot.jpg
  5. Go to the Site Server [PXE]
    1. Check if the following process is running, you will need to wait until this is done before trying to boot into WinPE using PXE
      bootwiz.jpg
  6. Once this is done, run a task to boot the client computer into PXE and see if all the changes you made are correct.
  7. Don't forget that there is also an X64 folder that may need to be modified if you use 64bit PE

 

Attached Articles files:

Utilities Files:

  • Q-Dir – file explorer for WinPE
  • RocketDock – strip down version for WinPE
  • SysInternalsSuite – list of tools that we use in our environment, so if you need more just added to this folder
  • UnxUtils – couple unix tools that comes in handy when need it

Utilities Files:

  • BGInfo – display the info on the background
  • ultravnc.exe – remote desktop
  • ultravnc.ini – settings for vnc
  • wmiexplorer – allow to load the wmi environment in WinPE

 

  • WKU_Get_BGInfo_Vars.vbs
    • This script will retrieve machine Serial Number and Altiris GUID Number
    • Create a file call “SetVars.bat”
  • WKU_WinPE.bat
    • First run the WKU_Get_BGInfo_Vars.vbs
    • Run the Set Vars.bat (created by the previous call)
    • Create a hostname file call “hostname.txt”
      • We notice that BGInfo was not reading the write hostname in WinPE, so this was the work around we found it.
    • Registry imports for custom settings
    • Start
      • RocketDock
      • VNC
      • BGInfo

Extra Files

  • WinPESettings.bat – this will mount the WINPE.WIM file, added the preset packages and unmounts
  • unattend.xml (optional) – this have just a setting, so the resolution of your WinPE environment will be set to 1024x768 32bit

 

Conclusion:

After BootWiz.exe finished building the WinPE environment, than you can test it and make sure all your configuration is working. I hope this can help people add tools and the Microsoft components into WinPE to take full advantage of WinPE 4.

Also want thanks everyone that post articles before, that help me develop this process.

Statistics
0 Favorited
6 Views
1 Files
0 Shares
0 Downloads
​
Attachment(s)
zip file
WinPETools.zip   9.27 MB   1 version
Uploaded - Feb 25, 2020
 
Download

Tags and Keywords

Comments

m.taylor
Jan 15, 2015 05:21 PM

Excellent article, a lot of really good information!

Due probably to a minor difference in the version of PECTAgent the log couldn't be parsed for the GUID in my environment. I changed the script to read the GUID from the registry and updated the regex to parse the log for the Altiris Resource Name instead. I'm currently on 7.5 SP1 HF4.

Including my modified WKU_Get_BGInfo_Vars.vbs below.

Thanks again for the great article ortolani!

 

WKU_Get_BGInfo_Vars.vbs

' Script to get this info and set them to environment variables:
'		- the computer's serial number/service tag
'		- the Altiris agent GUID
'
' Developed by: Ricardo Ortolani, Scott Copus
' last updated: 2014-03-06

	
    ' ------------------------------------------------------------------------------------------------------------------
    ' Global Objects
	Set objShell = WScript.CreateObject("WScript.Shell")
	Set objWMI = GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\cimv2")
	Const HKEY_LOCAL_MACHINE = &H80000002
	strComputer = "."
	Set oReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\default:StdRegProv")
	strAgentPath = "SOFTWARE\Altiris\Altiris Agent"
	AltirisAgentGUID = "none"
	AltirisName = "none"
    ' ------------------------------------------------------------------------------------------------------------------
    ' Main Program
    wscript.echo "------------------------------------------------------------------------------"
    wscript.echo "- ************** - WKU WinPE Environment Variables Setup - ***************** -"
    wscript.echo "------------------------------------------------------------------------------"
    wscript.echo "- This script will retrive Computer STN, GUID and Altiris Machine Name.                            -"
    wscript.echo "- Set as an environment variable.                                            -"
    wscript.echo "------------------------------------------------------------------------------"
    wscript.echo "- Version 1.0                                              Update 06/03/2014 -"
    wscript.echo "------------------------------------------------------------------------------"
    wscript.sleep 20000

    wscript.echo ""
    wscript.echo ""
    wscript.echo "-                                     STARTING - Environment Variables Setup -"
    wscript.echo "------------------------------------------------------------------------------"
    wscript.sleep 2000

    wscript.echo ""
    wscript.echo ""
    wscript.echo " - Retrieving Machine Serial Number"
    wscript.echo " -----------------------------------------------------------------------------"
    ' get Machine Serial Number
	SerialNumber = GetSerialNumber()
	If SerialNumber = "" Then
		wscript.echo " --> Failed to get the system serial number <--"
	End If
	wscript.echo " - Setting environment variable: COMP_STN=" & SerialNumber
	objShell.Environment("PROCESS").Item("COMP_STN") = SerialNumber
	objShell.Environment("USER").Item("COMP_STN") = SerialNumber
	objShell.Environment("SYSTEM").Item("COMP_STN") = SerialNumber
    wscript.sleep 2000
	
    wscript.echo ""
    wscript.echo ""
    wscript.echo " - Retrieving Machine GUID Number"
    wscript.echo " -----------------------------------------------------------------------------"
    ' get Altiris GUID Number
	Do
		oReg.GetStringValue HKEY_LOCAL_MACHINE, strAgentPath, "MachineGuid", strMachineGuid
		AltirisAgentGUID = strMachineGuid
		If AltirisAgentGUID = "none" Then
			wscript.echo " --> Altiris GUID not ready, trying again in 30 sec <--"
			wscript.sleep 30000
		End If
	Loop While AltirisAgentGUID = "none"
	wscript.sleep 20000
	
	If AltirisAgentGUID = "" Then
		wscript.echo " --> Failed to get the Altiris Agent GUID <--"
	End If
	wscript.echo " - Setting environment variable: COMP_AltirisGUID=" & AltirisAgentGUID
	objShell.Environment("PROCESS").Item("COMP_AltirisGUID") = AltirisAgentGUID
	objShell.Environment("USER").Item("COMP_AltirisGUID") = AltirisAgentGUID
	objShell.Environment("SYSTEM").Item("COMP_AltirisGUID") = AltirisAgentGUID
    wscript.sleep 2000

    wscript.echo ""
    wscript.echo ""
    wscript.echo " - Retrieving Altiris Machine Name"
    wscript.echo " -----------------------------------------------------------------------------"
    ' get Altiris Machine Name
	x = 0
	Do
		AltirisName = ParseAltirisLog()
		If AltirisName = "none" Then
			wscript.echo " --> Altiris Name not yet available, trying again in 30 sec <--"
			wscript.sleep 30000
		End If
		x = x + 1
	Loop While AltirisName = "none" and x < 10
	wscript.sleep 20000
	
	If AltirisName = "" Then
		wscript.echo " --> Failed to get the Altiris Machine Name <--"
	End If
	wscript.echo " - Setting environment variable: COMP_AltirisName=" & AltirisName
	objShell.Environment("PROCESS").Item("COMP_AltirisName") = AltirisName
	objShell.Environment("USER").Item("COMP_AltirisName") = AltirisName
	objShell.Environment("SYSTEM").Item("COMP_AltirisName") = AltirisName
    wscript.sleep 2000
	
    ' create bat file to set environment variables
	CreateBatchFileForVariables
    wscript.echo ""
    wscript.echo ""
    wscript.echo "------------------------------------------------------------------------------"
    wscript.echo "- Environment Variables Setup - Done                                         -"
    wscript.echo "------------------------------------------------------------------------------"
    wscript.echo "-                                            Developed by - Ricardo Ortolani -"
    wscript.echo "-                                                        Academic Technology -"
    wscript.echo "------------------------------------------------------------------------------"
    wscript.sleep 5000
	wscript.quit


' ----------------------------------------------------------------------------------------------------------------------
' GetSerialNumber
' ----------------------------------------------------------------------------------------------------------------------
Function GetSerialNumber()
	Set colBIOS = objWMI.ExecQuery("Select * from Win32_BIOS")
	SerialNumber = ""
	For Each objBIOS in colBIOS
		If Len(objBIOS.SerialNumber) > 0 Then
			SerialNumber = Trim(objBIOS.SerialNumber)
		End If
	Next
	GetSerialNumber = SerialNumber
End Function

' ----------------------------------------------------------------------------------------------------------------------
' ParseAltirisLog
' ----------------------------------------------------------------------------------------------------------------------
Function ParseAltirisLog()
	Const ForReading = 1
	tokens = "none"

	Set objRegEx = CreateObject("VBScript.RegExp")
	objRegEx.Pattern = "Resource guid=" & Chr(34) & "\{\w{8}\-\w{4}\-\w{4}\-\w{4}\-\w{12}\}" & Chr(34) & ".+name=\" & Chr(34) & "([0-9a-zA-Z-]+)\"""

	Set objFSO = CreateObject("Scripting.FileSystemObject")
	Set objFile = objFSO.OpenTextFile("X:\Program Files\Symantec\Deployment\Logs\PectAgent.log", ForReading)

	Do Until objFile.AtEndOfStream
		strSearchString = objFile.ReadLine
		Set colMatches = objRegEx.Execute(strSearchString)  
		If colMatches.Count > 0 Then
			If colMatches(0).SubMatches(0) <> "" Then
				tokens = colMatches(0).SubMatches(0)
				Exit Do
			End If
		End If
	Loop
	wscript.echo "result:" & tokens
	objFile.Close
	'ParseAltirisLog = tokens(1)
	ParseAltirisLog = tokens
End Function


' ----------------------------------------------------------------------------------------------------------------------
' CreateBatchFileForVariables
' ----------------------------------------------------------------------------------------------------------------------
Function CreateBatchFileForVariables()
	Const ForWriting = 2
	Set objFSO = CreateObject("Scripting.FileSystemObject")
	Set objFile = objFSO.OpenTextFile("X:\Utilities\SetVars.bat", ForWriting, True)
	objFile.Write "@echo off" & vbNewLine
	objFile.Write "SET COMP_STN=" & SerialNumber & vbNewLine
	objFile.Write "SET COMP_AltirisName=" & AltirisName & vbNewLine
	objFile.Write "SET COMP_AltirisGUID=" & AltirisAgentGUID & vbNewLine
	objFile.Close
End Function

 

Tomasz Woźniak
Jun 26, 2014 02:12 PM

I like it. Thumb up from me.

rscovel
Apr 17, 2014 11:24 AM

Greetings no-idea!

Could you perhaps provide the VBScript that you use? (It would be a big help since you have already done the work).. :)

 

Russ

SK
Mar 29, 2014 06:36 AM

Could you please provide the steps you used to implement the x64 bits into the provided x86 process.

JanTorsten Hobohm
Mar 29, 2014 04:33 AM

What I already use for some time is

- Lerup's Launchbar x64/64 with shortcuts to File Browser, CMD, Regedit, Notepad,Agent Logs...

- BgInfo x64/64

- UltraVNC x64/64

- Explorer++ x64/64

I call everything frm a VBscript out of runagent.bat Launchbar is a little bit tricky to configure because it relies on shortcuts but works well. The creation of these shortcuts is done before with the same VBscript.

Everything else depends on your needs and the availability.

 

rscovel
Mar 29, 2014 03:58 AM

Greetings,

 

Thanks for the great writeup about the tools to use. It will definitely be helpful to find x64 applications similar to those mentioned.

Since UEFI/GPT is only supported on the x64 WinPE 4 build using our Ghost standalone release or the DS 7.5 WinPE 4, these replacement tools are really needed. 

For those that want x86 and x64 tools in their WinPE could you post a link to the article you mentioned?


Your PXE menu project looks outstanding. I can't wait to see the finished project documentation.


Best Regards.

Russ

Tommy Edstrand
Mar 27, 2014 11:11 AM

Great article, thanks!

Have you seen/tried anything to speed upp the process for agent registration in DS 7.5?

ortolani
Mar 24, 2014 09:38 AM

The process will work with the x64, but the problem is with the utilities, and at the moment unless the company release an x64 version, we can’t use it or have to find alternatives.

I am current searching for x64 version of all the tools we have in our x86 environment. So far I found a 64 version of BGInfo and VNC, but there is still a lot of tools missing.

I found an article that show how to added x86 files, so x86 and x64 tools would work on WinPE, but that almost double the size of the WinPE. So I am not sure if this is a path to take. So if you find x64 versions of the tools please let me know or post on this article so it can be done in x86 and x64.

I am also working on my version of the “Initial Deployment Menu” converting to x64, since the version Symantec offers can be initiated by anyone as long they boot into PXE. So if you have Deployment Jobs in there a user could erase and image his HD by accident and lose all his data.

So my version take advantage of Symantec web services to trigger any task that you like (of course what u have publish for the user), but on my interface it ask for user name and password, and I do a 2 level of authentication, first the user has to exist in AD and be a valid user, second have rights the Altiris console. Than if both criteria’s are meet than triggers the jobs/task in the Altiris NS  (since web services only works with account that have Admin rights) I create a specific account to handle this, but on the description I insert the user username so I know who send the task. Is not perfect but it work great so far, I am converting to work with Workflow so I can post the code if people would like to use in their environment.

This is a small screenshot what the utility look like:

taskdeploy.jpg

thanks,

JanTorsten Hobohm
Mar 23, 2014 05:56 PM

Nice, but how about 64bit winPe? 32bit programs will not run there...
rocketdock - no but launchbar would, uvnc - yes, bginfo no. Explorer++ for file browsing...

SK
Mar 23, 2014 12:44 PM

This is a very good article.

The SSL issue is only relevant if SSL was NOT enabled during the initial installation phase of SMP plus solution(s)/suite(s).  There is also a workaround if SSL was enabled after the installation.

ortolani
Mar 19, 2014 09:10 AM

hello JM, the customizations will work without the hotfix, the reason I mention the hotfix version is because we are using SSL in our environment and HF3 broke the communication between PXE and NS. So I did test this when I first install 7.5 with no HF install, but by the time I wrote the article HF4 is current install in our environment.

thanks,

Ch@gGynelL_12
Mar 19, 2014 03:56 AM

Thank you for posting. But it was also applicable or can be done with the Altiris 7.5 only without the hotfix?

 

Thank you.

 

Regards,

JM

Klim_Belchev
Mar 15, 2014 10:11 PM

Great stuff - thank you!

JannasTo
Mar 07, 2014 10:13 AM

Very good article - thanks.

Related Entries and Links

No Related Resource entered.