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)

SBS 2003 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.

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,

Finally Answer for this problem that worked for me 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.
=============

Good Luck!!

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.

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.

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!!!

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 

Upgrade/Migration/Transtioning AD/Exchange 2003 Std to Ad/Exchange 2008Ent. x64 Part III

-->

Phase 3 :- Installation of Windows Exchange server standard 2007 SP1 & Move Mailbox, Installtion/Transfer of Commercial Certificate

A/ Install Exchange Pre-requisites and IIS

Install IIS Role from Go to Start > “Server Manager àFutures Roleà Install IIS role and Please make sure you install IIS 6.0 management compatibility, IIS6 Metabase Compatibility, Digest Authentication, Dynamic content compression à Restart the server.

Install Exchange Server Prerequisite

à Windows ServerPowerShell Management Tool

à.NET Framework 2 OR 3.5 (**Install this first .net 1.1
sp1, .net 2)

à MMC

àExchangeBPA,

àExchange2007-KB970162-x64-EN

And all the updates from AWD “BBN-Migration Utility” folder on AWD nas\pub

B/ Prepare Current Exchange Server 2003 Std environment to install and Transfer Mailbox to Exchange server 2007 Std.

Step 1:

Raise the Microsoft Exchange Server Operational Level From Mixed Level to Native Mode

On the Old Exchange server Open Exchange Server manager à R/C on “First Organisation (Exchange)” à Properties à Change the Operational Level From Mixed Level to Native Mode

Export (*.p12b) certificate from Old Exchange server with full certificate path and private key.

Step 2: Prepare Current Exchange server 2003 to transfer all records and schemas to new Exchange server 2007:-

Prepare AD and Domain Schema For Installing Exchange Server 2007 / 2010.

Run this command by pointing CMD to Exchange Server CD

1 / Setup.com /PrepareLegacyExchangePermissions

2/ Setup.com /PrepareSchema

3/ Setup.com /PrepareAD

4/ Setup.com /PrepareDomain

5/ Setup.com /PrepareAllDomains

c/ Install Exchange server 2007 SP1 Std.

Copy All Files and Folders from Exchange Server CD to the Local Hard Drive.

àR/C on Setup.exeà Compatibility TAB à Select “Run this program in Compatibility mode for Windows server 2008”)

(If you are installing Exchange Server 2010 run the Setup.exe Directly Without running compatibility Mode)

àR/C on EXCHANGESERVER.exe àCompatibility TAB à Select “Run this program in Compatibility mode for any Windows Previous Version.”

Ø Once Exchange Server is installed successfully check the Mail Box, Distribution list (Mailboxes Should be available in Legacy Mode)

Ø Check Recipients Connector to send and Receive Email’s.

d/ Change Mailbox size limit In Order to Start Moving Mail box from old to new server

àMEMC(Microsoft Exchange Management Console) àOrganisation Configurationà HUB Transport à Global Settings à Transport Settings à Properties and Change the Mailbox Size limit for Send and Receive.

Transfer Mailbox from old exchange server store to new exchange server store.

àMEMC(Microsoft Exchange Management Console) àRecipient Configuration à Mail Box à select the Mailbox you want to transfer to new store.

(Please do 4 Mailbox transfer at a time this task can take up to 18 to 23hrs)

e/ Install Commercial Certificate

Install Old server commercial certificate (*.p12b)

Ø On the new server

Start à mmc à Add snap in à Select Certificates à Select service for this computer à Select for this computer à ok.

Expand Certificates à Click on Intermediate Certificate à R/C Import à Select (*.p12b) certificate à Follow the wizard steps and finish the process.

Open IIS Management console à select IIS (Server Name)à on right pane click on “Server Certificates” à on the extreme right pane select Import à Select (*.p12b) certificate à Follow the wizard steps and finish the process.

f/ Change Client Access URL in order to take affect Commercial Certificate

Run the following command on Exchange server Mgt Console.

The following commands are for the single Exchange Server 2007 scenario

#holding the MBX, CA, HT roles

#Check the SCP details (Autodiscover Uri):

Get-ClientAccessServer | FL

#Set the new URI for SCP

Get-ClientAccessServer | Set-ClientAccessServer -AutoDiscoverServiceInternalUri https://mail.kbc.com.au/Autodiscover/Autodiscover.xml

#Check the Web Services URL:

Get-WebServicesVirtualDirectory | FL

#Set the new URL for Web Services:

Get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory -InternalUrl https:///EWS/Exchange.asmx -ExternalUrl https:///EWS/Exchange.asmx

#List Certificates in local store:

Get-ExchangeCertificate

Check and make sure you can see your Commercial Cetificate

#Asign an existing Certificate of Exchange Services:

Enable-ExchangeCertificate

Check the IPWS role attached to which Certificate and for taking role to your Commercial certificate run this command on the prompt:

Enable-ExchangeCertificate{Thumb Print of your Commercial certificate} Press Enter

When prompted please press “A” to yes to all role transfer from old to new Commercial certificate

Note / Troubleshooting : à Check the client computers of the domain for Outlook, it should pointing to new server. If not, please restart the client systems, that will do the change. It is good Idea to change/Move DNS, and DHCP services to new server. Also check the Exchange server to

MEMC(Microsoft Exchange Management Console) àOrganisation Configuration à Mailbox à on the right hand pane please select you server name à R/C Properties à System Settings and check à Active directory servers à Domain controller servers being used by Exchange server à should be your new server.

Also at the same place please check à Global Catalogue servers being used by Exchange server à should be your new server.

Please note that It will only take your new server as Active directory and Global catalogue server if your server has a Global catalogue server.

If your server is a Global Catalogue server and still having problem in this part (It is most probably It’s IPv6 problem that is not configured), Please go to command prompt and ping the server check

#ipconfig /all

Disable IPv6 on the server and restart the server and check it again.

1. Go to Network Connections folder (click on Start button, then right click on Network, select Properties, then click on “Manager Network Connections” on Tasks pane).
2. You should see various LAN, wireless, Bluetooth, high speed Internet, and other network connections available on the Vista computer with the network adapter description. Right click on the network connection that you want to disable the IPv6 interface and select “Properties”.

Click “Continue” on User Access Control permission request prompt.

3. Clear the check box next to the Internet Protocol version 6 (TCP/IPv6) component in the list under “This connection uses the following items” box.

-->

1. Click OK when done.
2. To re-enable IPv6, tick back the check box.

This method disables IPv6 on the particular LAN interface and connection. For other network adapter or connection, users have to repeat the steps to disable IPv6. Beside, disable IPv6 also does not disable IPv6 on tunnel interfaces or the IPv6 loopback interface.

It’s also possible to disable IPv6 and/or Teredo via Vista system registry. The registry settings also allow users to selectively disable components and configure behaviors for IPv6 in Windows Vista.

1. Open Registry editor (regedit).
2. Navigate to the following registry key branch:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
Services\tcpip6\Parameters\

3. Create the following registry value (DWORD type):

DisabledComponents

Note that the name must be exactly as shown, including capitalization. DisabledComponents is set to 0 by default.

4. The DisabledComponents registry value is a bit mask that controls the following series of flags, starting with the low order bit (Bit 0). To determine the value of DisabledComponents for a specific set of bits, the process is complicated, were hexadecimal value is calculated from binary number of the bits in correct position. For convenient, the following table lists some common configuration combinations and the corresponding DWORD value of DisabledComponents.

Configuration combination	DisabledComponents value
Disable all tunnel interfaces	0×1
Disable 6to4	0×2
Disable ISATAP	0×4
Disable Teredo	0×8
Disable Teredo and 6to4	0xA
Disable all LAN and PPP interfaces	0×10
Disable all LAN, PPP, and tunnel interfaces	0×11
Prefer IPv4 over IPv6	0×20
Disable IPv6 over all interfaces and prefer IPv4 to IPv6	0xFF

5. As seen from table above, to disable IPv6 support globally on all interface, set the value data for DisabledComponents to 000000FF, or simply FF. The registry entry will look like below:
6. 
   
   [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters]
   
   "DisabledComponents"=dword:000000ff
7. Restart the computer for changes to take effect.
8. To revert and enable IPv6, delete “DisabledComponents” registry key or set its registry value to 0.