|
I am planning on
installing SMS SP5, but first I would like to know how to manually re-apply
the SMS_DEF.MOF file. I am currently running SMS with SP4 and SMS Feature
Pack.
Contributed By: Hans Schefske [MVP SMS]
To avoid the loss of customized data follow the instructions below that are
also located in the README.HTM and README_OPERATIONS.HTM documents
accompanied with the Service Pack Installation files.
Copy the site
backup to tape before running the upgrade.
Copy your
customized files (NT_Logon.pcf, SMS_Def.mof, SMSbkup.ctl, SMSls.bat) to a
safe location where you can easily access them during the site upgrade.
Install SMS 2.0
SP5 with the Setup command-line option /dontstartsitecomp, which prevents
the Site Component Manager from starting when upgrade completes. When
Setup completes, your customized source files on the site server have been
overwritten with default files.
However, the command-line option prevents Site Component Manager from
starting. Therefore, default data, data on CAPs, and data on logon points
(where clients access files needed for their operations) is not
propagated.
Additionally, this prevents the Site Backup service from starting and
running with the default backup script.
After the upgrade
completes, copy your modified SMS 2.0 SP4 files:
NT_Logon.pcf to \SMS\Data\NT_Logon\NT_Logon.pcf
SMS_Def.mof to \SMS\Inboxes\Clifiles.src\Hinv\SMS_Def.mof
SMSbkup.ctl to \SMS\Inboxes\smsbkup.box\SMSbkup.ctl
SMSls.bat to \SMS\Data\NT_Logon\SMSls.bat
Copy all other modified site server source files to their correct
locations.
Manually restart
the SMS Site Component Manager. It then propagates your customized files
along with files updated by SP5.
|