Provided here you will find the steps necessary to perform a ConfigMgr 2007 Site Reset if the need arises.
A site reset in Configuration Manager is similar to the process for SMS 2003 and can be performed in a matter of minutes. The site reset process is initiated using the CD-ROM Installation media or the Configuration Manager Installation directory folder on the site system with the issues that need resolved.
Follow the steps below to perform a ConfigMgr 2007 site reset using the Microsoft Configuration Manager Installation directory folder.
1. Locate the Setup.Exe in the following default location: “C:\Program Files\Microsoft Configuration Manager\bin\I386\Setup.Exe”
2. At the Welcome to the Microsoft System Center Configuration Manager 2007 Setup Wizard screen review the information on the screen and select “Next’ to continue.
3. At the Available Setup Options screen select “Perform site maintenance or reset this site” radial button and select “Next” to continue.
4. At the Site Maintenance screen select the checkbox to “Modify SMS Provider configuration” and select “Next” to continue.
5. From the SMS Provider Settings Modification screen ensure that the site server name is populated in the text box provided for you to “Enter the appropriate installation location for the provider” and select “Next” to continue.
6. Select “Yes” to continue at the popup dialog box that states:
“Specified installation for the provider is the same as the current provider location.
Would you like to reinstall the provider?”
At this point the proves is initiated and the Setup Action Status Monitoring screen is displayed with the following actions and their status:
Shutdown Configuration Manager Services
Reset ConfigMgr related accounts
Reset permissions for ConfigMgr related directories
Upgrade site control file
Update Registry
Verify permissions for ConfigMgr related directories
7. When the process has been competed select “Next” to continue.
8. At the Completing the Microsoft System Center Configuration Manager 2007 Setup Wizard screen select the “View Log” button to review the log file and select “Launch the Configuration Manager Console after closing” to verify that ConfigMgr is operating as expected.
Note: If you choose not to review the log file at step 8 above you can review it at a later date. The site reset log file is appended to the existing C:\ ConfigMgrSetup.Log file.
Tip: Before performing a site reset it is a good practice to rename the existing ConfigMgrSetup log file to something like “Initial_ ConfigMgrSetup.Log” or “ConfigMgrSetup.Old” prior to performing a site reset. Then if needed you can rename the newly created site reset ConfigMgrSetup.Log file to something like “SiteReset_MMDDYY.Log”.
Advantages Of Performing An SMS 2003 Site Reset
http://myitforum.com/cs2/blogs/dhite/archive/2007/09/09/advantages-of-performing-an-sms-2003-site-reset.aspx
Specifying Your Own Password For The SMS Server Connection Account During A Site Reset
http://myitforum.com/cs2/blogs/dhite/archive/2006/12/04/specifying-your-own-password-for-the-sms-server-connection-account-during-a-site-reset.aspx
ConfigMgr Learn it and work it
28 October 2009
How to Perform a ConfigMgr 2007 Site Reset
Provided here you will find the steps necessary to perform a ConfigMgr 2007 Site Reset if the need arises.
A site reset in Configuration Manager is similar to the process for SMS 2003 and can be performed in a matter of minutes. The site reset process is initiated using the CD-ROM Installation media or the Configuration Manager Installation directory folder on the site system with the issues that need resolved.
Follow the steps below to perform a ConfigMgr 2007 site reset using the Microsoft Configuration Manager Installation directory folder.
1. Locate the Setup.Exe in the following default location: “C:\Program Files\Microsoft Configuration Manager\bin\I386\Setup.Exe”
2. At the Welcome to the Microsoft System Center Configuration Manager 2007 Setup Wizard screen review the information on the screen and select “Next’ to continue.
3. At the Available Setup Options screen select “Perform site maintenance or reset this site” radial button and select “Next” to continue.
4. At the Site Maintenance screen select the checkbox to “Modify SMS Provider configuration” and select “Next” to continue.
5. From the SMS Provider Settings Modification screen ensure that the site server name is populated in the text box provided for you to “Enter the appropriate installation location for the provider” and select “Next” to continue.
6. Select “Yes” to continue at the popup dialog box that states:
“Specified installation for the provider is the same as the current provider location.
Would you like to reinstall the provider?”
At this point the proves is initiated and the Setup Action Status Monitoring screen is displayed with the following actions and their status:
Shutdown Configuration Manager Services
Reset ConfigMgr related accounts
Reset permissions for ConfigMgr related directories
Upgrade site control file
Update Registry
Verify permissions for ConfigMgr related directories
7. When the process has been competed select “Next” to continue.
8. At the Completing the Microsoft System Center Configuration Manager 2007 Setup Wizard screen select the “View Log” button to review the log file and select “Launch the Configuration Manager Console after closing” to verify that ConfigMgr is operating as expected.
Note: If you choose not to review the log file at step 8 above you can review it at a later date. The site reset log file is appended to the existing C:\ ConfigMgrSetup.Log file.
Tip: Before performing a site reset it is a good practice to rename the existing ConfigMgrSetup log file to something like “Initial_ ConfigMgrSetup.Log” or “ConfigMgrSetup.Old” prior to performing a site reset. Then if needed you can rename the newly created site reset ConfigMgrSetup.Log file to something like “SiteReset_MMDDYY.Log”.
Advantages Of Performing An SMS 2003 Site Reset
http://myitforum.com/cs2/blogs/dhite/archive/2007/09/09/advantages-of-performing-an-sms-2003-site-reset.aspx
Specifying Your Own Password For The SMS Server Connection Account During A Site Reset
http://myitforum.com/cs2/blogs/dhite/archive/2006/12/04/specifying-your-own-password-for-the-sms-server-connection-account-during-a-site-reset.aspx
A site reset in Configuration Manager is similar to the process for SMS 2003 and can be performed in a matter of minutes. The site reset process is initiated using the CD-ROM Installation media or the Configuration Manager Installation directory folder on the site system with the issues that need resolved.
Follow the steps below to perform a ConfigMgr 2007 site reset using the Microsoft Configuration Manager Installation directory folder.
1. Locate the Setup.Exe in the following default location: “C:\Program Files\Microsoft Configuration Manager\bin\I386\Setup.Exe”
2. At the Welcome to the Microsoft System Center Configuration Manager 2007 Setup Wizard screen review the information on the screen and select “Next’ to continue.
3. At the Available Setup Options screen select “Perform site maintenance or reset this site” radial button and select “Next” to continue.
4. At the Site Maintenance screen select the checkbox to “Modify SMS Provider configuration” and select “Next” to continue.
5. From the SMS Provider Settings Modification screen ensure that the site server name is populated in the text box provided for you to “Enter the appropriate installation location for the provider” and select “Next” to continue.
6. Select “Yes” to continue at the popup dialog box that states:
“Specified installation for the provider is the same as the current provider location.
Would you like to reinstall the provider?”
At this point the proves is initiated and the Setup Action Status Monitoring screen is displayed with the following actions and their status:
Shutdown Configuration Manager Services
Reset ConfigMgr related accounts
Reset permissions for ConfigMgr related directories
Upgrade site control file
Update Registry
Verify permissions for ConfigMgr related directories
7. When the process has been competed select “Next” to continue.
8. At the Completing the Microsoft System Center Configuration Manager 2007 Setup Wizard screen select the “View Log” button to review the log file and select “Launch the Configuration Manager Console after closing” to verify that ConfigMgr is operating as expected.
Note: If you choose not to review the log file at step 8 above you can review it at a later date. The site reset log file is appended to the existing C:\ ConfigMgrSetup.Log file.
Tip: Before performing a site reset it is a good practice to rename the existing ConfigMgrSetup log file to something like “Initial_ ConfigMgrSetup.Log” or “ConfigMgrSetup.Old” prior to performing a site reset. Then if needed you can rename the newly created site reset ConfigMgrSetup.Log file to something like “SiteReset_MMDDYY.Log”.
Advantages Of Performing An SMS 2003 Site Reset
http://myitforum.com/cs2/blogs/dhite/archive/2007/09/09/advantages-of-performing-an-sms-2003-site-reset.aspx
Specifying Your Own Password For The SMS Server Connection Account During A Site Reset
http://myitforum.com/cs2/blogs/dhite/archive/2006/12/04/specifying-your-own-password-for-the-sms-server-connection-account-during-a-site-reset.aspx
SQL Server 2008 Memory Support
In Microsoft SQL Server 2008 the Standard, Enterprise, Developer and Web editions can use whatever the Operating Systems maximum allowed memory is.
Windows Server 2003
Windows Server 2003 Standard Edition can use a maximum of 4 GB.
Microsoft Windows Server 2003 Enterprise Edition can use a maximum of 32 GB for 32-bit (x86) machines and 64 GB for 64-bit Itanium machines.
Windows Server 2008
Windows Server 2008 Standard Edition can use a maximum of 4 GB.
Microsoft Windows Server 2008 Enterprise Edition can use a maximum of 64 GB for 32-bit (x86) machines and 2 TB for 64-bit Itanium machines.
The Workgroup edition can also use the Operating Systems maximum on 32-Bit systems and 4 GB on 64-bit systems.
The Express and Express with Advanced Services can use a maximum of 1 GB.
Windows Server 2003
Windows Server 2003 Standard Edition can use a maximum of 4 GB.
Microsoft Windows Server 2003 Enterprise Edition can use a maximum of 32 GB for 32-bit (x86) machines and 64 GB for 64-bit Itanium machines.
Windows Server 2008
Windows Server 2008 Standard Edition can use a maximum of 4 GB.
Microsoft Windows Server 2008 Enterprise Edition can use a maximum of 64 GB for 32-bit (x86) machines and 2 TB for 64-bit Itanium machines.
The Workgroup edition can also use the Operating Systems maximum on 32-Bit systems and 4 GB on 64-bit systems.
The Express and Express with Advanced Services can use a maximum of 1 GB.
SQL Server 2008 Memory Support
In Microsoft SQL Server 2008 the Standard, Enterprise, Developer and Web editions can use whatever the Operating Systems maximum allowed memory is.
Windows Server 2003
Windows Server 2003 Standard Edition can use a maximum of 4 GB.
Microsoft Windows Server 2003 Enterprise Edition can use a maximum of 32 GB for 32-bit (x86) machines and 64 GB for 64-bit Itanium machines.
Windows Server 2008
Windows Server 2008 Standard Edition can use a maximum of 4 GB.
Microsoft Windows Server 2008 Enterprise Edition can use a maximum of 64 GB for 32-bit (x86) machines and 2 TB for 64-bit Itanium machines.
The Workgroup edition can also use the Operating Systems maximum on 32-Bit systems and 4 GB on 64-bit systems.
The Express and Express with Advanced Services can use a maximum of 1 GB.
Windows Server 2003
Windows Server 2003 Standard Edition can use a maximum of 4 GB.
Microsoft Windows Server 2003 Enterprise Edition can use a maximum of 32 GB for 32-bit (x86) machines and 64 GB for 64-bit Itanium machines.
Windows Server 2008
Windows Server 2008 Standard Edition can use a maximum of 4 GB.
Microsoft Windows Server 2008 Enterprise Edition can use a maximum of 64 GB for 32-bit (x86) machines and 2 TB for 64-bit Itanium machines.
The Workgroup edition can also use the Operating Systems maximum on 32-Bit systems and 4 GB on 64-bit systems.
The Express and Express with Advanced Services can use a maximum of 1 GB.
27 October 2009
If Patch is not getting install and in MBSA report it is showing as required
If Patch is not getting install and in MBSA report it is showing as required we can i dentify and troublshoot below steps:--
1) Microsoft Suggested to run the System redindence tool -- this tool is 130+MB file, This Kb Might required reboot
http://support.microsoft.com/kb/947821
and After installing check the log file %SYSTEMROOT%\Logs\CBS\CheckSUR.log
2)Take ownership of the Packages folder("%SYSTEMROOT%\Servicing\Packages") and add your account to have full control
3)Based on the log file will get the missing files list i.e., .MUM and .Cat files.
4)Copy the .MUM and .CAT files to the %SYSTEMROOT%\Servicing\Packages folder from other working system to Problem system "%SYSTEMROOT%\Servicing\Packages" Folder
5) After Copy the .mum and Cat files we need to restart the " Windows Modules Installer" Service
Install the Patch 974291, if it is not installing re-run the redindence tool and analize the log file
6) IMPORTANT: Change the ownership of the %SYSTEMROOT%\Servicing\Packages
folder back to 'NT Service\TrustedInstaller'
Ofcource for the above steps you should perfom with your process where Change / Downtime.
1) Microsoft Suggested to run the System redindence tool -- this tool is 130+MB file, This Kb Might required reboot
http://support.microsoft.com/kb/947821
and After installing check the log file %SYSTEMROOT%\Logs\CBS\CheckSUR.log
2)Take ownership of the Packages folder("%SYSTEMROOT%\Servicing\Packages") and add your account to have full control
3)Based on the log file will get the missing files list i.e., .MUM and .Cat files.
4)Copy the .MUM and .CAT files to the %SYSTEMROOT%\Servicing\Packages folder from other working system to Problem system "%SYSTEMROOT%\Servicing\Packages" Folder
5) After Copy the .mum and Cat files we need to restart the " Windows Modules Installer" Service
Install the Patch 974291, if it is not installing re-run the redindence tool and analize the log file
6) IMPORTANT: Change the ownership of the %SYSTEMROOT%\Servicing\Packages
folder back to 'NT Service\TrustedInstaller'
Ofcource for the above steps you should perfom with your process where Change / Downtime.
If Patch is not getting install and in MBSA report it is showing as required
If Patch is not getting install and in MBSA report it is showing as required we can i dentify and troublshoot below steps:--
1) Microsoft Suggested to run the System redindence tool -- this tool is 130+MB file, This Kb Might required reboot
http://support.microsoft.com/kb/947821
and After installing check the log file %SYSTEMROOT%\Logs\CBS\CheckSUR.log
2)Take ownership of the Packages folder("%SYSTEMROOT%\Servicing\Packages") and add your account to have full control
3)Based on the log file will get the missing files list i.e., .MUM and .Cat files.
4)Copy the .MUM and .CAT files to the %SYSTEMROOT%\Servicing\Packages folder from other working system to Problem system "%SYSTEMROOT%\Servicing\Packages" Folder
5) After Copy the .mum and Cat files we need to restart the " Windows Modules Installer" Service
Install the Patch 974291, if it is not installing re-run the redindence tool and analize the log file
6) IMPORTANT: Change the ownership of the %SYSTEMROOT%\Servicing\Packages
folder back to 'NT Service\TrustedInstaller'
Ofcource for the above steps you should perfom with your process where Change / Downtime.
1) Microsoft Suggested to run the System redindence tool -- this tool is 130+MB file, This Kb Might required reboot
http://support.microsoft.com/kb/947821
and After installing check the log file %SYSTEMROOT%\Logs\CBS\CheckSUR.log
2)Take ownership of the Packages folder("%SYSTEMROOT%\Servicing\Packages") and add your account to have full control
3)Based on the log file will get the missing files list i.e., .MUM and .Cat files.
4)Copy the .MUM and .CAT files to the %SYSTEMROOT%\Servicing\Packages folder from other working system to Problem system "%SYSTEMROOT%\Servicing\Packages" Folder
5) After Copy the .mum and Cat files we need to restart the " Windows Modules Installer" Service
Install the Patch 974291, if it is not installing re-run the redindence tool and analize the log file
6) IMPORTANT: Change the ownership of the %SYSTEMROOT%\Servicing\Packages
folder back to 'NT Service\TrustedInstaller'
Ofcource for the above steps you should perfom with your process where Change / Downtime.
Subscribe to:
Posts (Atom)