It’s usually fairly easy to find out the current service pack level of a Microsoft Product. Normally, the product’s version information includes the information “Service Pack: #” or something similar. Not so with Exchange 2007. To find out an Exchange 2007′s service pack level, you must first find the build number and then compare the build number to this Microsoft KB article.
To find your build number from the Management Console select “Server Configuration”, right-click your server and select “Properties” and look on the “General” tab.
To find your build number from the Management Shell, run get-exchangeserver against the Exchange server in question. You will want to pipe the output into a different view to be able to see the full version number; for example get-exchangeserver | list. Look for the “AdminDisplayVersion:” line. The “Exchange Version” line, according to this article, refers to “the minimum version of the product that can read the object” and is not the number you need.
Then, compare the build number to Microsoft KB158530. As an example, I am running build 240.6 which equates to Exchange 2007 SP1.
For further reference, check out KB152439 “How to determine the version number, the build number, and the service pack level of Exchange Server”
some important links
http://support.microsoft.com/kb/158530
http://blogs.technet.com/b/scottschnoll/archive/2006/12/31/exchange-2007-platforms-and-product-keys.aspx
http://support.microsoft.com/kb/152439
Showing posts with label Windows Server. Show all posts
Showing posts with label Windows Server. Show all posts
Tuesday, 16 August 2011
Monday, 25 July 2011
How To Fix Windows 2003 acpitabl.dat Problem
Symptoms: Windows 2003 hangs after booting and never reach the login screen.
Background: ACPI stands for Advanced Configuration and Power Interface. It is an open standard that defines platform for hardware discovery, configuration, power management and monitoring.
Possible Cause and Resolution
Cause: CMOS Battery is Dying
Resolution: Goto CMOS setup, scroll to POWER MANAGEMENT SETUP, hit Enter, look at it, Hit ESC to exit, Anwser Y to save.
Source: Win2003 freezes at acpitabl.dat solution
Cause: RAID Problem
Resolution:
Turn off the server.
Unplug one of the hard disk in your RAID.
Boot the server. The RAID status now should change to degraded
You should now be able to see the login screen.
Login, do the necessary backup
Plugin the hard disk, rebuild the RAID array with its software
Background: ACPI stands for Advanced Configuration and Power Interface. It is an open standard that defines platform for hardware discovery, configuration, power management and monitoring.
Possible Cause and Resolution
Cause: CMOS Battery is Dying
Resolution: Goto CMOS setup, scroll to POWER MANAGEMENT SETUP, hit Enter, look at it, Hit ESC to exit, Anwser Y to save.
Source: Win2003 freezes at acpitabl.dat solution
Cause: RAID Problem
Resolution:
Turn off the server.
Unplug one of the hard disk in your RAID.
Boot the server. The RAID status now should change to degraded
You should now be able to see the login screen.
Login, do the necessary backup
Plugin the hard disk, rebuild the RAID array with its software
Saturday, 16 July 2011
Disabling the Windows Firewall
Disabling the Firewall Using the Control Panel
This method is for any user with administrative access to unmanaged systems such as: home, RESNET, and campus unmanaged system, and self-managed.
- From the Start menu, select Control Panel, then select Windows Firewall.
- Select Off, then click Ok.
Disabling the Firewall Using Local Policy
This method is for IT administrators with administrative access to unmanaged systems or locally managed systems where the machine is not part of a Windows 2000 or higher domain.
- From the Start menu, select Run, then enter gpedit.msc.
- Expand the Computer Configuration folder, then the Administrative Templates folder.
- Expand the Network folder, then the Network Connections folder, then the Windows Firewall folder.
- Select the Standard Profile folder.
- Double-click the Windows Firewall: Protect all network connections option.
- Select Disabled, then click OK.
- Select the Domain Profile folder.
- Double-click the Windows Firewall: Protect all network connections option.
- Select Disabled, then click OK.
- Close the Group Policy dialog box.
Disabling the Firewall Using Group Policy
This method is for IT administrators with administrative access to UT-managed machines that are part of a Windows 2000 or 2003 Active Directory domain.
- Create a new Group Policy object, and give the object a descriptive name (for example, ITS-Turn off Windows Firewall).
- Select the newly created group policy.
- Right-click on the newly created policy and select Edit.
- Expand the Computer Configuration folder, then the Administrative Templates folder.
- Expand the Network folder, then the Network Connections folder, then the Windows Firewall folder.
- Select the Standard Profile folder.
- Double-click the Windows Firewall: Protect all network connections option.
- Select Disabled, then click OK.
- Select the Domain Profile folder.
- Double-click the Windows Firewall: Protect all network connections option.
- Select Disabled, then click OK.
- Close the Group Policy dialog box.
- In the Security Filter section, click Add.
- Search for the objects that this group policy will be applied to, then click OK.
- Close the Group Policy editor.
Thursday, 30 June 2011
deploying Firefox with FirefoxADM
deploying Firefox with FirefoxADM
gpo settings for default homepage firefox
find here with Attachment containing all required documents
FirefoxADM_0.5.9.4
gpo settings for default homepage firefox
find here with Attachment containing all required documents
FirefoxADM_0.5.9.4
Set Default IE Home Page VIA GPO
Hello Friends,
Settings to make any web page as a defult home page of all domain workstation VIA GPO is:
Default Domain Policy Or any relavant GPO
go to -->
User Config:
Windows Settings:
IE Maintenance:
URLs:
Important URLs:
Home page URL: set to my homepage.
Apply --> ok
you can force GPO to apply by running "gpupdate /force" on command pormpt.
Settings to make any web page as a defult home page of all domain workstation VIA GPO is:
Default Domain Policy Or any relavant GPO
go to -->
User Config:
Windows Settings:
IE Maintenance:
URLs:
Important URLs:
Home page URL: set to my homepage.
Apply --> ok
you can force GPO to apply by running "gpupdate /force" on command pormpt.
Tuesday, 17 May 2011
How to find DN path for Users, Security Gruop, etc.
cmd /k dsquery group -name "Security Group Name"
cmd /k dsquery User -name "Username"
cmd /k dsquery User -name "Username"
Terminal Services RemoteApp Session Termination Logic
Terminal Services RemoteApp™ Session Termination Logic
There are several heuristics and session time limit Group Policy settings that dictate the lifetime of a RemoteApp session. The main difference in behavior between a RemoteApp session and a regular full desktop session is that there is no explicit way for the user to either log off or disconnect a RemoteApp session.
The procedure for when to end a RemoteApp session involves two stages. In the first stage, heuristics are applied to determine whether the session needs to be disconnected. If the session needs to be disconnected, stage two is triggered. In stage two, Group Policy settings are used to decide if and when to log off the disconnected RemoteApp session.
Stage I: When should the RemoteApp session be disconnected?
Several factors are considered in deciding when to disconnect a RemoteApp session. The session disconnection is triggered when all RemoteApp windows and user launched system tray icons are closed. The following flow chart shows the decision-making process. Each step is discussed in detail below.
1. A RemoteApp session remains active as long as there is at least one visible or active window in that session.
- The active window could be in any of the window states (minimized, maximized or restored).
- The active window could belong to an application that was either started directly or indirectly as a RemoteApp program.
Scenario: A user double-clicks the Remote Outlook icon to start Microsoft® Office Outlook®. [Outlook is the directly started application]. The user then opens an e-mail with a Word attachment and opens the document. This starts Word in the session. [Word is the indirectly started application]. The session will remain active until both the Outlook and Word windows are closed.
2. A RemoteApp session remains active as long as there is at least one notification area (system tray) icon of an application that was started directly or indirectly by the user.
Scenario: A user double-clicks the Remote Microsoft Office Communicator icon. After the application is started, the remote notification area icon for Communicator is also shown in the client’s notification area. Even if the main window of Communicator is closed, the application is still running in the background. The session will remain active.
Note that a remote notification area icon that is not explicitly started by the user is not taken into consideration as part of decision 2.
Scenario: A user double-clicks the Remote Outlook icon to start Outlook. As part of the logon script, the antivirus software client also starts and appears in the notification area. If the remote Outlook window is closed by the user, the remote notification area icon that belongs to the antivirus program is ignored because it was not started (either directly or indirectly) by the user.
3. If the answers to decision 1 and decision 2 are both “No,” there are no RemoteApp programs running in the session. At this point, there is a 20 second wait, in case the user wants to start another RemoteApp program on the same server, or if the recently closed RemoteApp program displays any messages upon closure. If the user chooses not to start any more remote programs in this period, the RemoteApp session will be disconnected and the client process (mstsc.exe) will exit.
Stage II – Setting the time delay for the logoff from a disconnected RemoteApp session
You can use the Session Time Limits policy settings for Terminal Services sessions to set the time limit for RemoteApp sessions. Typically, administrators use these policy settings for scalability reasons.
New Group Policy setting—RemoteApp session logoff delay
There is a new policy setting introduced in Windows Server 2008 that allows for the administrator to set the time delay for the logoff from a disconnected RemoteApp session. As it is much faster to connect to a disconnected session as opposed to starting a new session, you can use this policy setting to provide a faster startup times when a user launches a new RemoteApp on the same server. Based on server performance, an administrator must determine a time limit that provides the best user experience, while not overwhelming server resources by permitting these "no remote program running" RemoteApp sessions to remain in a disconnected state.
What is the default setting for the “Set time limit for logoff of RemoteApp sessions” policy setting?
By default, RemoteApp sessions will remain in a disconnected state indefinitely.
Where are the session time limit policy settings located?
To locate the session time limit policy settings, follow these steps:
1. Log on to the terminal server as an administrator.
2. Start the Local Group Policy Editor. To do this, click Start, click Run, type gpedit.msc, and then click OK.
3. Locate the following node:
Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Session Time Limits
Note: The policy settings are also located under User Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Session Time Limits
4. The new policy—Set time limit for logoff of RemoteApp sessions—is shown in the following figure:
How do I enable the time limit for logoff delay?
To enable the “Set time limit for logoff of RemoteApp sessions” policy setting, follow these steps:
1. In the right pane of the Local Group Policy Editor, double-click Set time limit for logoff of RemoteApp sessions.
2. Click Enabled.
3. In the RemoteApp session logoff delay list, select the desired time for logoff delay, and then click OK.
4. At a command prompt, type gpupdate, and then press ENTER to force the policy to refresh immediately on the local computer.
After the policy setting is enabled, disconnected RemoteApp sessions will be logged off after the configured time delay.
Scenario: Consider a typical work day where a user closes their RemoteApp programs when they leave work at 5:00 P.M. When they return to work at 8:00 A.M. the following day, they start their RemoteApp programs again. Assume that the administrator has chosen 18 hours as the time limit for RemoteApp session logoff. When the user returns in the morning and restarts their programs, the remote programs will start quickly. Even if the user logs on after 19 hours, there is no possibility for data loss because there are no remote programs running in the session. Unlike existing session time limit policies, there is no threat of data loss because the policy setting applies only to RemoteApp sessions that have no remote programs running that were started by the user. Therefore, you should configure this new policy setting with the goal of providing the better user experience.
Is there any possibility of conflict between the RemoteApp logoff policy setting and other session limit policy settings?
We recommend that you set other session limit policy settings that end the session to a time limit that is higher than the RemoteApp logoff delay policy setting. If this is not the case, there is a possibility for conflict.
Scenario: Extending the scenario mentioned earlier, assume that the administrator has also set the “Set time limit for disconnected sessions” policy setting to two days. When a user leaves work at 5:00 P.M. on Friday, by the time that they return to work at 8:00 A.M. on Monday, their session would be logged off. In this manner, the administrator can choose to log off the disconnected sessions that are taking up server resources. If the administrator decides to end the session in 12 hours instead of two days, the RemoteApp logoff policy setting that was set for 18 hours has no effect. After 12 hours, the session will be logged off.
Terminal Services RemoteApp Session Termination Logic
Terminal Services RemoteApp™ Session Termination Logic
There are several heuristics and session time limit Group Policy settings that dictate the lifetime of a RemoteApp session. The main difference in behavior between a RemoteApp session and a regular full desktop session is that there is no explicit way for the user to either log off or disconnect a RemoteApp session.
The procedure for when to end a RemoteApp session involves two stages. In the first stage, heuristics are applied to determine whether the session needs to be disconnected. If the session needs to be disconnected, stage two is triggered. In stage two, Group Policy settings are used to decide if and when to log off the disconnected RemoteApp session.
Stage I: When should the RemoteApp session be disconnected?
Several factors are considered in deciding when to disconnect a RemoteApp session. The session disconnection is triggered when all RemoteApp windows and user launched system tray icons are closed. The following flow chart shows the decision-making process. Each step is discussed in detail below.
1. A RemoteApp session remains active as long as there is at least one visible or active window in that session.
- The active window could be in any of the window states (minimized, maximized or restored).
- The active window could belong to an application that was either started directly or indirectly as a RemoteApp program.
Scenario: A user double-clicks the Remote Outlook icon to start Microsoft® Office Outlook®. [Outlook is the directly started application]. The user then opens an e-mail with a Word attachment and opens the document. This starts Word in the session. [Word is the indirectly started application]. The session will remain active until both the Outlook and Word windows are closed.
2. A RemoteApp session remains active as long as there is at least one notification area (system tray) icon of an application that was started directly or indirectly by the user.
Scenario: A user double-clicks the Remote Microsoft Office Communicator icon. After the application is started, the remote notification area icon for Communicator is also shown in the client’s notification area. Even if the main window of Communicator is closed, the application is still running in the background. The session will remain active.
Note that a remote notification area icon that is not explicitly started by the user is not taken into consideration as part of decision 2.
Scenario: A user double-clicks the Remote Outlook icon to start Outlook. As part of the logon script, the antivirus software client also starts and appears in the notification area. If the remote Outlook window is closed by the user, the remote notification area icon that belongs to the antivirus program is ignored because it was not started (either directly or indirectly) by the user.
3. If the answers to decision 1 and decision 2 are both “No,” there are no RemoteApp programs running in the session. At this point, there is a 20 second wait, in case the user wants to start another RemoteApp program on the same server, or if the recently closed RemoteApp program displays any messages upon closure. If the user chooses not to start any more remote programs in this period, the RemoteApp session will be disconnected and the client process (mstsc.exe) will exit.
Stage II – Setting the time delay for the logoff from a disconnected RemoteApp session
You can use the Session Time Limits policy settings for Terminal Services sessions to set the time limit for RemoteApp sessions. Typically, administrators use these policy settings for scalability reasons.
New Group Policy setting—RemoteApp session logoff delay
There is a new policy setting introduced in Windows Server 2008 that allows for the administrator to set the time delay for the logoff from a disconnected RemoteApp session. As it is much faster to connect to a disconnected session as opposed to starting a new session, you can use this policy setting to provide a faster startup times when a user launches a new RemoteApp on the same server. Based on server performance, an administrator must determine a time limit that provides the best user experience, while not overwhelming server resources by permitting these "no remote program running" RemoteApp sessions to remain in a disconnected state.
What is the default setting for the “Set time limit for logoff of RemoteApp sessions” policy setting?
By default, RemoteApp sessions will remain in a disconnected state indefinitely.
Where are the session time limit policy settings located?
To locate the session time limit policy settings, follow these steps:
1. Log on to the terminal server as an administrator.
2. Start the Local Group Policy Editor. To do this, click Start, click Run, type gpedit.msc, and then click OK.
3. Locate the following node:
Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Session Time Limits
Note: The policy settings are also located under User Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Session Time Limits
4. The new policy—Set time limit for logoff of RemoteApp sessions—is shown in the following figure:
How do I enable the time limit for logoff delay?
To enable the “Set time limit for logoff of RemoteApp sessions” policy setting, follow these steps:
1. In the right pane of the Local Group Policy Editor, double-click Set time limit for logoff of RemoteApp sessions.
2. Click Enabled.
3. In the RemoteApp session logoff delay list, select the desired time for logoff delay, and then click OK.
4. At a command prompt, type gpupdate, and then press ENTER to force the policy to refresh immediately on the local computer.
After the policy setting is enabled, disconnected RemoteApp sessions will be logged off after the configured time delay.
Scenario: Consider a typical work day where a user closes their RemoteApp programs when they leave work at 5:00 P.M. When they return to work at 8:00 A.M. the following day, they start their RemoteApp programs again. Assume that the administrator has chosen 18 hours as the time limit for RemoteApp session logoff. When the user returns in the morning and restarts their programs, the remote programs will start quickly. Even if the user logs on after 19 hours, there is no possibility for data loss because there are no remote programs running in the session. Unlike existing session time limit policies, there is no threat of data loss because the policy setting applies only to RemoteApp sessions that have no remote programs running that were started by the user. Therefore, you should configure this new policy setting with the goal of providing the better user experience.
Is there any possibility of conflict between the RemoteApp logoff policy setting and other session limit policy settings?
We recommend that you set other session limit policy settings that end the session to a time limit that is higher than the RemoteApp logoff delay policy setting. If this is not the case, there is a possibility for conflict.
Scenario: Extending the scenario mentioned earlier, assume that the administrator has also set the “Set time limit for disconnected sessions” policy setting to two days. When a user leaves work at 5:00 P.M. on Friday, by the time that they return to work at 8:00 A.M. on Monday, their session would be logged off. In this manner, the administrator can choose to log off the disconnected sessions that are taking up server resources. If the administrator decides to end the session in 12 hours instead of two days, the RemoteApp logoff policy setting that was set for 18 hours has no effect. After 12 hours, the session will be logged off.
Thursday, 12 May 2011
Distribution Group\List Accept email from external domain names
Distribution Group\List Accept email from external domain names
run the following command on exchange management shell (EMS) Please write exactly same as shown below.
(Case Sensitive)
#Set-DistributionGroup "<Distribution Group Name>" -RequireSenderAuthenticationEnabled $False
Cheers!!!
run the following command on exchange management shell (EMS) Please write exactly same as shown below.
(Case Sensitive)
#Set-DistributionGroup "<Distribution Group Name>" -RequireSenderAuthenticationEnabled $False
Cheers!!!
Saturday, 16 April 2011
Friday, 15 April 2011
Exchagne 2007 Commands
The following commands are for the single Exchange Server 2007 scenario
#holding the MailBox, Client Access, Hub Transport roles
#Check the SCP details (Autodiscover Uri):
Get-ClientAccessServer | FL
#Set the new URI for SCP
Get-ClientAccessServer | Set-ClientAccessServer -AutoDiscoverServiceInternalUri https://yourFQDNServer/Autodiscover/Autodiscover.xml
#Check the Web Services URL:
Get-WebServicesVirtualDirectory | FL
#Set the new URL for Web Services:
Get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory -InternalUrl https://yourFQDN/EWS/Exchange.asmx -ExternalUrl https://yourFQDN/EWS/Exchange.asmx
#To Install Commercial Certificates for Active Sync OR for Security purpose
#List Certificates in local store:
Get-ExchangeCertificate
#Asign an existing Certificate ofr Exchange Services:
#Enable-ExchangeCertificate
And follow the Screen Steps This will ask for Thumb print of the certificate that you want to enable for any purpose like POP, IIS, SMTP, IMAP
POP = POP3
SMTP = SMTP
IIS= Wemail and Active Sync
IMAP=IMAP
#Additional links:
#How to Install GoDaddy SSL Certificate in IIS6
http://www.netometer.com/video/tutorials/godaddy-ssl-certificate/index.php
#How to Install GoDaddy SSL Certificate in IIS7
http://www.netometer.com/video/tutorials/iis7-godaddy-ssl-certificate/
#run fillowing command from shell to allow and accept External email by Distribution list.
Set-DistributionGroup <"ditribution list name"> -RequireSenderAuthenticationEnabled $False
#holding the MailBox, Client Access, Hub Transport roles
#Check the SCP details (Autodiscover Uri):
Get-ClientAccessServer | FL
#Set the new URI for SCP
Get-ClientAccessServer | Set-ClientAccessServer -AutoDiscoverServiceInternalUri https://yourFQDNServer/Autodiscover/Autodiscover.xml
#Check the Web Services URL:
Get-WebServicesVirtualDirectory | FL
#Set the new URL for Web Services:
Get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory -InternalUrl https://yourFQDN/EWS/Exchange.asmx -ExternalUrl https://yourFQDN/EWS/Exchange.asmx
#To Install Commercial Certificates for Active Sync OR for Security purpose
#List Certificates in local store:
Get-ExchangeCertificate
#Asign an existing Certificate ofr Exchange Services:
#Enable-ExchangeCertificate
And follow the Screen Steps This will ask for Thumb print of the certificate that you want to enable for any purpose like POP, IIS, SMTP, IMAP
POP = POP3
SMTP = SMTP
IIS= Wemail and Active Sync
IMAP=IMAP
#Additional links:
#How to Install GoDaddy SSL Certificate in IIS6
http://www.netometer.com/video/tutorials/godaddy-ssl-certificate/index.php
#How to Install GoDaddy SSL Certificate in IIS7
http://www.netometer.com/video/tutorials/iis7-godaddy-ssl-certificate/
#run fillowing command from shell to allow and accept External email by Distribution list.
Set-DistributionGroup <"ditribution list name"> -RequireSenderAuthenticationEnabled $False
Tuesday, 4 January 2011
Off topic: When Windows NLB won’t NLB (Quick Tip)…
Off topic: When Windows NLB won't NLB (Quick Tip)...
Windows Server 2008 Terminal server load balancing on Cluster enviroment
Windows Server 2008 Terminal server load balancing on Cluster enviroment
Monday, 3 January 2011
Wednesday, 22 December 2010
How To remove WSUS Manually
1. Download the SDK to obtain MSIZAP
To obtain the Windows Server 2003 SP1 Platform SDK, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5
2. From a command prompt, type:
For WSUS 2.0: MSIZAP T { A0D46DC6-8950-451A-8990-53C86E17666E}
For WSUS 3.0: MSIZAP T {2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}
3. From a command prompt, type: sc delete wsusservice
4. Again, From a command prompt, type: MSIZAP T {2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}
5. Run following command to ensure the Windows internal database is removed.
On 32-bit platforms: msiexec /x {CEB5780F-1A70-44A9-850F-DE6C4F6AA8FB} callerid=ocsetup.exe
On 64-bit platforms: msiexec /x {BDD79957-5801-4A2D-B09E-852E7FA64D01} callerid=ocsetup.exe
6. Reboot the server.
7. From a command prompt, type: aspnet_regiis –i
8. From a command prompt, type: iisreset
To obtain the Windows Server 2003 SP1 Platform SDK, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5
2. From a command prompt, type:
For WSUS 2.0: MSIZAP T { A0D46DC6-8950-451A-8990-53C86E17666E}
For WSUS 3.0: MSIZAP T {2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}
3. From a command prompt, type: sc delete wsusservice
4. Again, From a command prompt, type: MSIZAP T {2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}
5. Run following command to ensure the Windows internal database is removed.
On 32-bit platforms: msiexec /x {CEB5780F-1A70-44A9-850F-DE6C4F6AA8FB} callerid=ocsetup.exe
On 64-bit platforms: msiexec /x {BDD79957-5801-4A2D-B09E-852E7FA64D01} callerid=ocsetup.exe
6. Reboot the server.
7. From a command prompt, type: aspnet_regiis –i
8. From a command prompt, type: iisreset
Friday, 17 December 2010
SBS 2003 BPA question Managed Recipient Policies
Hi to all,
I am planning a migration to sbs 2008 in the near future, still working on
choosing the hardware phase.
Just ran the SBS BPA today and got a warning that I can't seem to find an
answer for:
Managed Recipient Policies
The Mailbox Manager setting is enabled for one or more recipient policies.
As a result, the recipient policies will not be upgraded if you migrate to
Windows SBS 2008 and Exchange Server 2007.
I checked some blogs and tpis twaks,
Answer for this problem is
=============
If you have Exchange 2003 or Exchange 2000 policies that are BOTH E-mail Addresses and Mailbox Manager policies (they have both the Mailbox Manager Settings
(Policy) tab and the E-mail Addresses (Policy) tab), perform the following steps to remove the mailbox manager portion of the policy:
1. In Exchange System Manager, expand Recipients, and then select Recipient Policies.
2. Right-click the policy, and then select Change property pages.
3. Clear the Mailbox Manager Settings check box, and then click OK. Please reffere to above images.
How to check for duplicate/invalid SMTP addresses in recipient policies:
1. In Exchange System Manager, expand Recipients, and then select Recipient Policies.
2. Right-click the policy, and then select E-Mail Addresses (Policy) tab.
3. Inspect the SMTP Addresses for any that are unchecked. If you find any, place a check in the box or remove that address.
4. Inspect the SMTP Addresses for any that have an IP address. For instance, @192.168.1.1. If you find any, remove those addresses that contain an IP address.
5. Click OK.
=============
Thanks.
I am planning a migration to sbs 2008 in the near future, still working on
choosing the hardware phase.
Just ran the SBS BPA today and got a warning that I can't seem to find an
answer for:
Managed Recipient Policies
The Mailbox Manager setting is enabled for one or more recipient policies.
As a result, the recipient policies will not be upgraded if you migrate to
Windows SBS 2008 and Exchange Server 2007.
I checked some blogs and tpis twaks,
Answer for this problem is
If you have Exchange 2003 or Exchange 2000 policies that are BOTH E-mail Addresses and Mailbox Manager policies (they have both the Mailbox Manager Settings
(Policy) tab and the E-mail Addresses (Policy) tab), perform the following steps to remove the mailbox manager portion of the policy:
1. In Exchange System Manager, expand Recipients, and then select Recipient Policies.
2. Right-click the policy, and then select Change property pages.
3. Clear the Mailbox Manager Settings check box, and then click OK. Please reffere to above images.
How to check for duplicate/invalid SMTP addresses in recipient policies:
1. In Exchange System Manager, expand Recipients, and then select Recipient Policies.
2. Right-click the policy, and then select E-Mail Addresses (Policy) tab.
3. Inspect the SMTP Addresses for any that are unchecked. If you find any, place a check in the box or remove that address.
4. Inspect the SMTP Addresses for any that have an IP address. For instance, @192.168.1.1. If you find any, remove those addresses that contain an IP address.
5. Click OK.
=============
Thanks.
SBS BPA Known Issues/Common Questions
1) You get a warning
Windows Server Update Services 2.0 installed
This server is running Windows Server Update Services 2.0. You should upgrade Windows Server Update Services 2.0 to Windows Server Update Services 3.0. For information about upgrading Windows Server Update Services 2.0 to Windows Server Update Services 3.0, see ”Installing Windows Server Update Services 3.0 on Windows SBS 2003” at the Microsoft Web site (http://go.microsoft.com/fwlink/?linkid=77404).
This should refer to the link http://go.microsoft.com/fwlink/?linkid=89081 instead of http://go.microsoft.com/fwlink/?linkid=77404. This will be addressed in the first update to the BPA.
2) You get one or both of the following warnings
Windows SBS 2003 R2 Technologies installed
Windows SBS 2003 has the Windows SBS 2003 R2 Technologies installed but Service Pack 2 for Windows SharePoint Services 2.0 is not installed.
or
Daylight Savings Time not updated
Windows SharePoint Services has not been updated for Daylight Savings Time. For more information see the Knowledge Base articles "Description of the update for Windows SharePoint Services: January 9 2007" at http://go.microsoft.com/fwlink/?LinkId=95936 and "Description of the Windows SharePoint Services post-Service Pack 2 hotfix package: March 9 2007" at http://go.microsoft.com/fwlink/?LinkId=95163.
Please click on the Tree Reports radio button and then go under Windows Small Business Server Baseline/Technologies/Windows SharePoint Services 2.0/HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\6.0 and see if the value for the Version = 6.0.2.8165 or greater. If so, then it appears that you have WSS SP3 (or later) installed and you should be able to ignore the above warnings.
If the Version is less than 6.0.2.6568 then it would appear the WSS SP2 has not been installed. This will be addressed in the first update to the BPA.
3) You get a warning
Small Business registry key exists
The Small Business registry key exists and should be removed. You should either back up or export this registry key and then delete the Small Business registry key located at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Small Business.
We will include a link to http://support.microsoft.com/default.aspx/kb/914990 in order for you to get more information about this registry key. This will be addressed in the first update to the BPA.
4) You get a warning even though you have Windows Server 2003 SP1 or SP2 installed
Windows SBS 2003 Service Pack 1 not installed
Windows SBS 2003 SP1 is available. For download information, see http://go.microsoft.com/fwlink/?linkid=50694. To order the Windows SBS 2003 cd set (required for Windows SBS 2003 Premium Edition customers), go to http://go.microsoft.com/fwlink/?linkid=50685.
This is by design. Windows SBS 2003 SP1 is an SBS specific service pack. It is made up of 5 parts including the operating system service pack, Exchange Server service pack, Windows SharePoint Services service pack, XP SP2 update, and Windows SBS 2003 SP1 itself. The Exchange Server service packs, XP SP2 update for SBS, and Windows SBS 2003 SP1 itself are not distributed via Microsoft Update. You must download these components from the Microsoft Download Center. Please note that the ability to order the Windows SBS 2003 SP1 cd set (required for Premium customers in order to get ISA 2004) ends at the end of this year. Additional information can also be found at http://blogs.technet.com/sbs/archive/2007/07/03/sbs-2003-sp-0-support-retirement.aspx
5) You get a warning of
DNS Client not configured
The DNS client is not configured to point only to the internal IP address of the server. For detailed instructions about configuring the DNS client, see the "Configurations" section of the Knowledge Base article "How to configure Internet access in Windows Small Business Server 2003" at http://go.microsoft.com/fwlink/?LinkId=95289.
Internal Network Adapter is not configured to register IP address in DNS
Verify that the internal network card is configured to register in DNS. For detailed instructions about verifying internal adapter configuration, see the procedure for "Internal or single network adapter configuration" in the "Configurations" section of the Knowledge Base article "How to configure Internet access in Windows Small Business Server 2003" at http://go.microsoft.com/fwlink/?LinkId=95289.
Ensure that the LANNIC registry value has the proper network card GUID. Check using Method 3 in the KB article http://support.microsoft.com/default.aspx/kb/875422.
6) Get a warning of
Outlook Mobile Access is not using .Net Framework version 1.1.4322
Microsoft Outlook Mobile Access should be using .Net Framework version 1.1.4322. To do so, click Start, point to Administrative Tools, click Internet Information Services (IIS) Manager. In the IIS Manager snap-in, double-click Web Sites, double-click Default Web Site, right-click oma, and then click Properties. Click the ASP.NET tab, and then for ASP.Net version, select 1.1.4322
And/or
Remote Web Workplace not using .Net Framework 1.1.4322
Remote Web Workplace should be using .Net Framework version 1.1.4322. To do so, click Start, point to Administrative Tools, click Internet Information Services (IIS) Manager. In the IIS Manager snap-in, double-click Web Sites, double-click Default Web Site, right-click Remote, and then click Properties. Click the ASP.NET tab, and then for ASP.Net version, select 1.1.4322.
And/or
The Windows SBS Backup site is not using .Net Framework 1.1.4322
The Windows SBS Backup site should be using .Net Framework version 1.1.4322. To do so, click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager. In the IIS Manager snap-in, double-click Web Sites, double-click Default Web Site, right-click Backup, and then click Properties. Click the ASP.NET tab, and then for ASP.Net version, select 1.1.4322.
And/or
Windows SBS Monitoring is not using .Net Framework 1.1.4322
Windows SBS Monitoring should be using .Net Framework version 1.1.4322. To do so, click Start, point to Administrative Tools, click Internet Information Services (IIS) Manager. In the IIS Manager snap-in, double-click Web Sites, double-click Default Web Site, right-click Monitoring, and then click Properties. Click the ASP.NET tab, and then for ASP.Net version, select 1.1.4322.
This is by design. These features were designed and tested against the ASP.Net Framework v1.1.4322. Note that Remote Web Workplace, Backup, Monitoring and Companyweb all need to be using the same version of ASP.Net Framework due to the fact that they are all in the same application pool. If you change them from v2.0 back to the v1.1.4322 then you may also need to follow the steps in the More Information section of http://support.microsoft.com/kb/894903 in order to change Companyweb back to ASP.Net v1.1.4322.
7) Is there a way to silently install and/or schedule the SBS BPA to run?
Currently, there is not a way to silently install and/or run it as
a scheduled task.
8) When will the first update of the BPA be available?
Currently the first update for the BPA is planned to occur by the end of this year.
Windows Server Update Services 2.0 installed
This server is running Windows Server Update Services 2.0. You should upgrade Windows Server Update Services 2.0 to Windows Server Update Services 3.0. For information about upgrading Windows Server Update Services 2.0 to Windows Server Update Services 3.0, see ”Installing Windows Server Update Services 3.0 on Windows SBS 2003” at the Microsoft Web site (http://go.microsoft.com/fwlink/?linkid=77404).
This should refer to the link http://go.microsoft.com/fwlink/?linkid=89081 instead of http://go.microsoft.com/fwlink/?linkid=77404. This will be addressed in the first update to the BPA.
2) You get one or both of the following warnings
Windows SBS 2003 R2 Technologies installed
Windows SBS 2003 has the Windows SBS 2003 R2 Technologies installed but Service Pack 2 for Windows SharePoint Services 2.0 is not installed.
or
Daylight Savings Time not updated
Windows SharePoint Services has not been updated for Daylight Savings Time. For more information see the Knowledge Base articles "Description of the update for Windows SharePoint Services: January 9 2007" at http://go.microsoft.com/fwlink/?LinkId=95936 and "Description of the Windows SharePoint Services post-Service Pack 2 hotfix package: March 9 2007" at http://go.microsoft.com/fwlink/?LinkId=95163.
Please click on the Tree Reports radio button and then go under Windows Small Business Server Baseline/Technologies/Windows SharePoint Services 2.0/HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\6.0 and see if the value for the Version = 6.0.2.8165 or greater. If so, then it appears that you have WSS SP3 (or later) installed and you should be able to ignore the above warnings.
If the Version is less than 6.0.2.6568 then it would appear the WSS SP2 has not been installed. This will be addressed in the first update to the BPA.
3) You get a warning
Small Business registry key exists
The Small Business registry key exists and should be removed. You should either back up or export this registry key and then delete the Small Business registry key located at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Small Business.
We will include a link to http://support.microsoft.com/default.aspx/kb/914990 in order for you to get more information about this registry key. This will be addressed in the first update to the BPA.
4) You get a warning even though you have Windows Server 2003 SP1 or SP2 installed
Windows SBS 2003 Service Pack 1 not installed
Windows SBS 2003 SP1 is available. For download information, see http://go.microsoft.com/fwlink/?linkid=50694. To order the Windows SBS 2003 cd set (required for Windows SBS 2003 Premium Edition customers), go to http://go.microsoft.com/fwlink/?linkid=50685.
This is by design. Windows SBS 2003 SP1 is an SBS specific service pack. It is made up of 5 parts including the operating system service pack, Exchange Server service pack, Windows SharePoint Services service pack, XP SP2 update, and Windows SBS 2003 SP1 itself. The Exchange Server service packs, XP SP2 update for SBS, and Windows SBS 2003 SP1 itself are not distributed via Microsoft Update. You must download these components from the Microsoft Download Center. Please note that the ability to order the Windows SBS 2003 SP1 cd set (required for Premium customers in order to get ISA 2004) ends at the end of this year. Additional information can also be found at http://blogs.technet.com/sbs/archive/2007/07/03/sbs-2003-sp-0-support-retirement.aspx
5) You get a warning of
DNS Client not configured
The DNS client is not configured to point only to the internal IP address of the server. For detailed instructions about configuring the DNS client, see the "Configurations" section of the Knowledge Base article "How to configure Internet access in Windows Small Business Server 2003" at http://go.microsoft.com/fwlink/?LinkId=95289.
Internal Network Adapter is not configured to register IP address in DNS
Verify that the internal network card is configured to register in DNS. For detailed instructions about verifying internal adapter configuration, see the procedure for "Internal or single network adapter configuration" in the "Configurations" section of the Knowledge Base article "How to configure Internet access in Windows Small Business Server 2003" at http://go.microsoft.com/fwlink/?LinkId=95289.
Ensure that the LANNIC registry value has the proper network card GUID. Check using Method 3 in the KB article http://support.microsoft.com/default.aspx/kb/875422.
6) Get a warning of
Outlook Mobile Access is not using .Net Framework version 1.1.4322
Microsoft Outlook Mobile Access should be using .Net Framework version 1.1.4322. To do so, click Start, point to Administrative Tools, click Internet Information Services (IIS) Manager. In the IIS Manager snap-in, double-click Web Sites, double-click Default Web Site, right-click oma, and then click Properties. Click the ASP.NET tab, and then for ASP.Net version, select 1.1.4322
And/or
Remote Web Workplace not using .Net Framework 1.1.4322
Remote Web Workplace should be using .Net Framework version 1.1.4322. To do so, click Start, point to Administrative Tools, click Internet Information Services (IIS) Manager. In the IIS Manager snap-in, double-click Web Sites, double-click Default Web Site, right-click Remote, and then click Properties. Click the ASP.NET tab, and then for ASP.Net version, select 1.1.4322.
And/or
The Windows SBS Backup site is not using .Net Framework 1.1.4322
The Windows SBS Backup site should be using .Net Framework version 1.1.4322. To do so, click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager. In the IIS Manager snap-in, double-click Web Sites, double-click Default Web Site, right-click Backup, and then click Properties. Click the ASP.NET tab, and then for ASP.Net version, select 1.1.4322.
And/or
Windows SBS Monitoring is not using .Net Framework 1.1.4322
Windows SBS Monitoring should be using .Net Framework version 1.1.4322. To do so, click Start, point to Administrative Tools, click Internet Information Services (IIS) Manager. In the IIS Manager snap-in, double-click Web Sites, double-click Default Web Site, right-click Monitoring, and then click Properties. Click the ASP.NET tab, and then for ASP.Net version, select 1.1.4322.
This is by design. These features were designed and tested against the ASP.Net Framework v1.1.4322. Note that Remote Web Workplace, Backup, Monitoring and Companyweb all need to be using the same version of ASP.Net Framework due to the fact that they are all in the same application pool. If you change them from v2.0 back to the v1.1.4322 then you may also need to follow the steps in the More Information section of http://support.microsoft.com/kb/894903 in order to change Companyweb back to ASP.Net v1.1.4322.
7) Is there a way to silently install and/or schedule the SBS BPA to run?
Currently, there is not a way to silently install and/or run it as
a scheduled task.
8) When will the first update of the BPA be available?
Currently the first update for the BPA is planned to occur by the end of this year.
Thursday, 16 December 2010
Remove Trend Micro Client Security Agent Forcefully Or Manually
Hello Friends,
Some time you want to remove / unload Trend Micro Client agent from system(Computer).
Please fnid here with the details.
To remove / reset the uninstall password for Trend Micro OfficeScan
Edit Ofcscan.ini file. (Do a search.)
On Windows.95/98/XP machines it is usually in C:\Windows\Ofcscan.ini
On Windows.NT/2K machines it is usually in C:\WINNT\Ofcscan.ini
Open the Ofcscan.ini file using notepad search for the [INI_CLIENT_SECTION]
Find the line reading Uninstall_Pwd= and type a # at the beginning of the line to comment it out.
Insert a new line saying Uninstall_Pwd=70
Save the Ofcscan.ini file and retry the uninstall. When it prompts you for a password, enter a '1'.
Method 2 for Uninstall Trend Micro Client when you don't know password
Start --> Run --> regedit -->
HKLM--> Software--> Trend Micro --> PCClinNTCrop --> Misc.
in right side pannel search for Registry "AllowUninstall" edit key to 1 instead of 0.
Now try to uninstall Trend Micro Via Add and Remove Programe.
If this method don't work
reboot your workstation / system to safe mode and remove Trend Micro
Good Luck!!!
Some time you want to remove / unload Trend Micro Client agent from system(Computer).
Please fnid here with the details.
To remove / reset the uninstall password for Trend Micro OfficeScan
Edit Ofcscan.ini file. (Do a search.)
On Windows.95/98/XP machines it is usually in C:\Windows\Ofcscan.ini
On Windows.NT/2K machines it is usually in C:\WINNT\Ofcscan.ini
Open the Ofcscan.ini file using notepad search for the [INI_CLIENT_SECTION]
Find the line reading Uninstall_Pwd= and type a # at the beginning of the line to comment it out.
Insert a new line saying Uninstall_Pwd=70
Save the Ofcscan.ini file and retry the uninstall. When it prompts you for a password, enter a '1'.
Method 2 for Uninstall Trend Micro Client when you don't know password
Start --> Run --> regedit -->
HKLM--> Software--> Trend Micro --> PCClinNTCrop --> Misc.
in right side pannel search for Registry "AllowUninstall" edit key to 1 instead of 0.
Now try to uninstall Trend Micro Via Add and Remove Programe.
If this method don't work
reboot your workstation / system to safe mode and remove Trend Micro
Good Luck!!!
Wednesday, 15 December 2010
Migrating Your Existing Infrastructure SBS 2003 to the SBS 2008 Environment
Migrating Your Existing Infrastructure to the SBS Environment
Click the above link to get step by step document on Migration/Upgrade your Existing SBS2003 Infrastructure to SBS 2008 Environment.
http://www.google.com.au/url?sa=t&source;=web&cd;=1&ved;=0CBcQFjAA&url;=http%3A%2F%2Fdownload.microsoft.com%2Fdocuments%2FFrance%2FTechNet%2F2009%2FSBS%2FHands-on-labs_Windows_SBS_2008_Migration_from_SBS2003.pdf&rct;=j&q;=windows%20SBS%202008%20Migrating%20Your%20Existing%20Infrastructure%20to%20the%20SBS%20Environment&ei;=WRsHTd7hA4_jrAeZqJ3bDQ&usg;=AFQjCNHvDVFZq2jovuZyx9mHTqylzKhqlA&sig2;=5JWBOdD6yG84W_pGrTIQEg&cad;=rja
Saturday, 11 December 2010
Troubleshooting journal_wrap errors shows in AD Migration Preparation tools SBS2003-2008
When performing Windows SBS 2003 to SBS 2008 Migration/Upgrade.
At the stage of:
Run Migration Preparation tool from Windows SBS 2008 DVD
Gives an error of AD in Journal Wrap mode and perform following steps.
The solution is
Delete Event logs from server all logs just delete.
1. Click Start, and then click Run.
2. In the Open box, type cmd and then press ENTER.
3. In the Command box, type net stop ntfrs.
4. Click Start, and then click Run.
5. In the Open box, type regedit and then press ENTER.
6. Locate the following subkey in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
7. In the right pane, double-click BurFlags.
8. In the Edit DWORD Value dialog box, type D2 and then click OK.
9. Quit Registry Editor, and then switch to the Command box.
10. In the Command box, type net start ntfrs.
11. Quit the Command box.
When the FRS service restarts, the following actions occur:
* The value for BurFlags registry key returns to 0.
* Files in the reinitialized FRS folders are moved to a Pre-existing folder.
* An event 13565 is logged to signal that a nonauthoritative restore is started.
* The FRS database is rebuilt.
* The member performs an initial join of the replica set from an upstream partner or from the computer that is specified in the Replica Set Parent registry key if a parent has been specified for SYSVOL replica sets.
* The reinitialized computer runs a full replication of the affected replica sets when the relevant replication schedule begins.
* When the process is complete, an event 13516 is logged to signal that FRS is operational. If the event is not logged, there is a problem with the FRS configuration.
Note: The placement of files in the Pre-existing folder on reinitialized members is a safeguard in FRS designed to prevent accidental data loss. Any files destined for the replica that exist only in the local Pre-existing folder and did not replicate in after the initial replication may then be copied to the appropriate folder. When outbound replication has occurred, delete files in the Pre-existing folder to free up additional drive space.
Also try this too.
Increasing the USN journal size, and thus the number of changes that it can hold before the journal "wraps", decreases the possibility that the USN journal wrap will occur. The USN journal size can be changed by setting the following registry key:
HKLM\System\CCS\Services\NTFRS\Parameters\"Ntfs Journal size in MB" (REG_DWORD)
Valid settings range from 8 to 128 megabytes (MB) with a default of 32 MB. This setting applies to all volumes that are hosting an FRS replica tree. You have to stop and then restart the NTFRS service for the increases to the USN journal size take affect. Decreases to the USN journal size can only be made by reformatting all volumes that contain FRS-replicated content.
The number of changes that a given USN journal file can hold can be estimated with the following formula:
journal size/((60 bytes + (length of file name)) * 2)
At the stage of:
Run Migration Preparation tool from Windows SBS 2008 DVD
Gives an error of AD in Journal Wrap mode and perform following steps.
The solution is
Delete Event logs from server all logs just delete.
1. Click Start, and then click Run.
2. In the Open box, type cmd and then press ENTER.
3. In the Command box, type net stop ntfrs.
4. Click Start, and then click Run.
5. In the Open box, type regedit and then press ENTER.
6. Locate the following subkey in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
7. In the right pane, double-click BurFlags.
8. In the Edit DWORD Value dialog box, type D2 and then click OK.
9. Quit Registry Editor, and then switch to the Command box.
10. In the Command box, type net start ntfrs.
11. Quit the Command box.
When the FRS service restarts, the following actions occur:
* The value for BurFlags registry key returns to 0.
* Files in the reinitialized FRS folders are moved to a Pre-existing folder.
* An event 13565 is logged to signal that a nonauthoritative restore is started.
* The FRS database is rebuilt.
* The member performs an initial join of the replica set from an upstream partner or from the computer that is specified in the Replica Set Parent registry key if a parent has been specified for SYSVOL replica sets.
* The reinitialized computer runs a full replication of the affected replica sets when the relevant replication schedule begins.
* When the process is complete, an event 13516 is logged to signal that FRS is operational. If the event is not logged, there is a problem with the FRS configuration.
Note: The placement of files in the Pre-existing folder on reinitialized members is a safeguard in FRS designed to prevent accidental data loss. Any files destined for the replica that exist only in the local Pre-existing folder and did not replicate in after the initial replication may then be copied to the appropriate folder. When outbound replication has occurred, delete files in the Pre-existing folder to free up additional drive space.
Also try this too.
Increasing the USN journal size, and thus the number of changes that it can hold before the journal "wraps", decreases the possibility that the USN journal wrap will occur. The USN journal size can be changed by setting the following registry key:
HKLM\System\CCS\Services\NTFRS\Parameters\"Ntfs Journal size in MB" (REG_DWORD)
Valid settings range from 8 to 128 megabytes (MB) with a default of 32 MB. This setting applies to all volumes that are hosting an FRS replica tree. You have to stop and then restart the NTFRS service for the increases to the USN journal size take affect. Decreases to the USN journal size can only be made by reformatting all volumes that contain FRS-replicated content.
The number of changes that a given USN journal file can hold can be estimated with the following formula:
journal size/((60 bytes + (length of file name)) * 2)
Thursday, 29 April 2010
How To remove WSUS Manually
1. Download the SDK to obtain MSIZAP
To obtain the Windows Server 2003 SP1 Platform SDK, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5
2. From a command prompt, type:
For WSUS 2.0: MSIZAP T { A0D46DC6-8950-451A-8990-53C86E17666E}
For WSUS 3.0: MSIZAP T {2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}
3. From a command prompt, type: sc delete wsusservice
4. Again, From a command prompt, type: MSIZAP T {2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}
5. Run following command to ensure the Windows internal database is removed.
On 32-bit platforms: msiexec /x {CEB5780F-1A70-44A9-850F-DE6C4F6AA8FB} callerid=ocsetup.exe
On 64-bit platforms: msiexec /x {BDD79957-5801-4A2D-B09E-852E7FA64D01} callerid=ocsetup.exe
6. Reboot the server.
7. From a command prompt, type: aspnet_regiis –i
8. From a command prompt, type: iisreset
To obtain the Windows Server 2003 SP1 Platform SDK, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5
2. From a command prompt, type:
For WSUS 2.0: MSIZAP T { A0D46DC6-8950-451A-8990-53C86E17666E}
For WSUS 3.0: MSIZAP T {2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}
3. From a command prompt, type: sc delete wsusservice
4. Again, From a command prompt, type: MSIZAP T {2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}
5. Run following command to ensure the Windows internal database is removed.
On 32-bit platforms: msiexec /x {CEB5780F-1A70-44A9-850F-DE6C4F6AA8FB} callerid=ocsetup.exe
On 64-bit platforms: msiexec /x {BDD79957-5801-4A2D-B09E-852E7FA64D01} callerid=ocsetup.exe
6. Reboot the server.
7. From a command prompt, type: aspnet_regiis –i
8. From a command prompt, type: iisreset
Subscribe to:
Posts (Atom)