Change back to SBS folder from download folder

[Cody Dirrigle]

Since I have been a altiris admin after you recreate pxe  bootwiz would kick off and all the files we needed for imaging would be created under on the NBS's

C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\SBS\Bootwiz\{random}\cache\bootwiz

With 8.5 ru4 this changed to now everything goes to:

C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\Downloads\{random}\cache

To get updated imaging files after pxe recreate I need to copy the bootwiz folder under downloads to the SBS folder

Is there some setting that I'm not seeing that allows me to set it back to going to the not SBS folder and not downloads?

[Sergei Zjaikin]

There is no any setting.
All the packages managed by deployment agent in production or automation now go into C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\Downloads\<package GUID>>\cache folder. The GUID is not random, it is the package GUID.
After a package is downloaded it can be either used from this folder or copied into another folder if another copy is really needed.

Why would you need to copy bootwiz files to the old folder?  Is something not working? Could you please provide the log files?

thanks!

[Cody Dirrigle]

If I don’t copy it to the sbs folder we don’t get any of the updated imaging files. For example I update the winpe background with every update, if I want those changes to show I copy the new one to the bdc folder on the NS, recreate pxe, then on each Nbs I need to go into that download folder, copy the new updated files from there to sbs folder so the changed background shows when you pxe boot. Before 8.5 ru4 everything went to sbs on its own. Understand it’s guid, I just replaced the guid with the word random so I didn’t have to type it out.

which logs do you want?

[Sergei Zjaikin]

The logs are located in C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\Logs

After you changed the package on NS and "NS.Package Refresh"  and "NS.Package Distribution Point Update " Task Scheduler tasks completed the package should be automatically propagates to the site servers, no any additional manual steps are required. Those tasks run once per day, you can run them manually via Task Scheduler or command-line:

                schtasks /Run /TN "NS.Package Refresh.{bd6bf880-bfae-4dad-b746-e8be99f3b8a8}"

                schtasks /Run /TN "NS.Package Distribution Point Update Schedule.{29a2b641-222a-43b0-830c-a25c59e93fe4}"

And if all the software is updated on pxe server to RU4 then all of them should be using the proper files from "Downloads" folder. 
Could you please provide the logs please so we could see what's going on there?

thanks!

[Cody Dirrigle]

So that is the thing, the packages do update to the NBS its just they go to download folder but the imaging process wants those files to be the sbs folder

I had opened a ticket with support about this after ru4 but they didn't seem to know either where the files should be and then the ticket got closed since the person left the company I think so it why I have just been copying them from the download folder to sbs since then. 

This is from one of vendors who is imaging right now for the log

One other thing that has been a minor cosmetic thing since ru4 I also attached, the pxe rebuild has never stopped showing icon for running, even though everything is complete and its not running

[Sergei Zjaikin]

Cody, I do not quite see in the logs that anything fails or uses the old paths incorrectly, here is bootwiz.exe starting and using files downloaded into "Downloads" folder and creating files in "\SBS\Images\WinPE 10"

[2021/03/11 06:36:27.613 3680:1216  INFO] Preboot Images Policy: Starting application 'C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\Downloads\{374E1C49-4F58-4F5C-8D51-07A30F0D44AD}\cache\BootWiz\BootWiz.exe' with command-line ' -quiet -pxe "WinPE 10" -rootpath "C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\SBS\Images\WinPE 10" -cfg "C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\Downloads\{374E1C49-4F58-4F5C-8D51-07A30F0D44AD}\cache\BootWizWinPE 10\WinPE 10.cfg" -os "WinPE10" -x64 "x64" -oem "DS" -create' in 'C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\Downloads\{374E1C49-4F58-4F5C-8D51-07A30F0D44AD}\cache\BootWiz'
[2021/03/11 06:36:27.629 3680:1216 <TRC>] Preboot Images Policy: Process created
[2021/03/11 06:45:00.386 3680:1216  INFO] Preboot Images Policy: The process completed with exit code 0

A moment later the created image is modified successfully.

[2021/03/11 06:45:00.401 3680:1216  INFO] PECTAgent.ini injection: Processing 'C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\SBS\Images\WinPE 10'
[2021/03/11 06:45:00.417 3680:1216 <TRC>] PECTAgent.ini injection: 'C:\boot\altiris\iso\@inject@\Program Files\Symantec\Deployment\PECTAgent.ini' is missing, error: The system cannot find the path specified (0x00000003)
[2021/03/11 06:45:00.417 3680:1216 <TRC>] PECTAgent.ini injection: Temporary folder 'C:\Windows\TEMP\AeX_{D7EFF1FF-809D-4101-9068-F9F044788D51}_3680.tmp' created
[2021/03/11 06:45:00.417 3680:1216 <TRC>] PECTAgent.ini injection: Mount folder 'C:\Windows\TEMP\AeX_{06105A4D-9E45-4A40-82B2-AF2C60682D4F}_3680.tmp' created
[2021/03/11 06:45:14.659 3680:1216  INFO] PECTAgent.ini injection: 'C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\SBS\Images\WinPE 10\x64\sources\boot.wim' mounted
[2021/03/11 06:45:14.659 3680:1216  INFO] PECTAgent.ini injection: 'C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\PECTAgent.ini' was copied to 'C:\Windows\TEMP\AeX_{06105A4D-9E45-4A40-82B2-AF2C60682D4F}_3680.tmp\Program Files\Symantec\Deployment\PECTAgent.ini'
[2021/03/11 06:45:38.497 3680:1216  INFO] PECTAgent.ini injection: 'C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\SBS\Images\WinPE 10\x64\sources\boot.wim' unmounted

Could you please tell me exactly which files do you need to copy every time?

thanks!

[Cody Dirrigle]

winpe.bmp
winpe.jpg

If I don't copy these its the old ghost background, I create my own every update. 

I don't see it updating the drivers either, I had to copy a new driver I had added to the sbs folder, it was in the download folder but the site could use the new usb dongle until I moved it to the drivers folder under sbs

[Sergei Zjaikin]

Your scenario should work without any manual step.
What happens if the old folder is not there? Is it possible to move the old folder temporarily to some other place and then try reproducing the problem?
We're interested to see the logs.
Please also send bootwiz log, it should be in the same folder -  C:\Program Files\Altiris\Deployment\Logs\Bootwiz.log 

thanks!

[Cody Dirrigle]

I didn't forget about this, we are just in the middle of a go live with about 900 devices being deployed so don't want to mess with imaging until we are done and then will test this and report back