DS 7.5 + 7.6: How to do a complete repair of Deployment Solution

book

Article ID: 178726

calendar_today

Updated On:

Products

Deployment Solution

Issue/Introduction

 

Resolution

NOTE: Running a repair should be used as a last resort.  Please telephone support before using.


1.) Using the SIM, repair DS using the source Service Pack of DS first, then repair any Hotfixes (Example: Repair DS7.5 SP1 first, then repair DS7.5 SP1 HF5). This is to ensure that nothing in the file system is missing from the SMP.

2.) Using AEXCONFIG.exe, Reconfigure the DS on the Notification Server by downloading 'DSConfiguration.bat' from this KB and executing it on the NS. This bat file ensures file system setups and database related items are restored and working properly, to an extent. You can even watch this process happen in the Altiris Log Viewer if you filter by AeXconfig.exe.

These items together can take up to hours to complete. The reconfigure specifically can take a while, and may show some command prompt boxes that appear to be doing nothing. Do not close these boxes, they are working. Closing them prematurely will cause items to not configure properly or at all.
 

3.) Check to make sure all files and folders were put in place correctly through the repair and reconfigure. Locations and things you need to check:

a.) Check to ensure both Pectagent.ini files have complete information located in:
C:\Program Files\Altiris\Deployment\BDC\bootwiz\oem\DS\winpe\x86\Base\Program Files\Symantec\Deployment
C:\Program Files\Altiris\Deployment\BDC\bootwiz\oem\DS\winpe\x64\Base\Program Files\Symantec\Deployment

  • If either Pectagent.ini have @SMPPORT for the port value or @SMPPROTOCOL for the protocol value in the INI file, they need to be replaced with correct port and protocol, default 80 and http, respectively. They do need to reflect what you are using in your environment if not using the default setup. Make sure your Servername under the Name value is correct as well.
     

b.) Check for MSI.DLL and Shutdown.exe in the following locations:
C:\Program Files\Altiris\Deployment\BDC\bootwiz\oem\DS\winpe\x86\Base\Windows\System32
C:\Program Files\Altiris\Deployment\BDC\bootwiz\oem\DS\winpe\x64\Base\Windows\System32

  • If not present, they are attached to this article. Download and place them in their respective architecture paths, placing the 2 files directly into System32.
     

c.) Ensure Symbolic Links were created for the BDC and DriversDB folders in the following folder:
C:\Program Files\Altiris\Notification Server\NSCap\bin\Deployment

  • Run the following commands if you do not see BDC and DriversDB folders in the above location:
    mklink /d /j BDC "c:\Program Files\Altiris\Deployment\BDC"
    mklink /d /j DriversDB "c:\Program Files\Altiris\Deployment\DriversDB"

 

Now we wait. It takes a bit for services and policies to get all caught up with themselves. In most cases, it's best to let the SMP server do it's proper updates in order overnight. Otherwise, you may be able to speed processes up by running the NS.Package Refresh and the NS.Complete Membership Resource Update in the Windows Task Scheduler Library on your SMP server.

 

 

Attachments

System32backupWinPE.zip get_app
DSConfiguration.bat get_app
System32backupWinPE.zip get_app
DSConfiguration.bat get_app