Go to Start / All Programs / Accessories. Right Click the ‘Command Prompt’ item and click the ‘Run As Administrator’ option.
In the Command Prompt window, Paste the following command.
REGSVR32 %SYSTEMROOT%\SYSTEM32\WUAUENG.DLL
Press ENTER.
You should see a popup that says the command succeeded.
Exit the command prompt and try Windows Update again.
- Due to the following error, the DFS Replication reporting mechanism cannot access the WMI (Windows Management Instrumentation) namespace to retrieve certain reporting information. Error ID: 0x80041002. - DFS Replication cannot replicate with partner <server name> for replication group <domain>\<name space>\<share>. The partner did not recognize the connection or the replication group configuration. The DFS Replication service used partner DNS name <server name>, IP address <the server ip>, and WINS address <server name> but failed with error ID: 9026 (The connection is invalid). Event ID: 5012 AND - The DFS Replication service is stopping communication with partner <server name> for replication group Domain System Volume due to an error. The service will retry the connection periodically. Additional Information: Error: 1726 (The remote procedure call failed.) Connection ID: 580D7FC3-873F-48CC-AFC1-73E96DFADCE2 Replication Group ID: ACA5FC8A-AA2E-4D40-8ECC-3A0A8F45E5F
Solution below sorted my problem:
Open a CMD prompt in %windir%\system32\wbem
type mofcomp dfsrprovs.mof as below
C:\Windows\System32\wbem> mofcomp dfsrprovs.mof net stop winmgmt net start winmgmt net start iphlpsvc net stop dfsr net start dfsr
Managing public folders in Exchange Server 2007 SP1 still requires the use of PowerShell cmdlets snap-in exposed in the Exchange Management Shell. This practical example illustrates how to resolve common issues around public folder access rights.
Scenario A: Outlook shows public folder as “Access Denied”(you do not have permissions to …)
[PS] C:\Windows\System32>Get-PublicFolderClientPermission -Identity “\folder\sharedItems” | fl
Identity : \folder\sharedItems
User : Default
AccessRights : {FolderVisible}Identity : \folder\sharedItems
User : Anonymous
AccessRights : {FolderVisible}Identity : \folder\sharedItems
User : swissitpro.ch/OU1/pic
AccessRights : {CreateItems, EditOwnedItems, EditAllItems, FolderContact, FolderVisible}Identity : \folder\sharedItems
User : swissitpro.ch/group/it/grpitadmin
AccessRights : {Owner}Identity : \folder\sharedItems
User : swissitpro.ch/OU1/groupOfPFUsers
AccessRights : {Author}
Removing existing access rights and then assigning the Person-In-Charge (PIC) the Author role with pre-defined access rights solved the problem:
[PS] C:\Windows\System32>Remove-PublicFolderClientPermission -Identity “\folder\sharedItems” -user “pic” -accessrights CreateItems, EditOwnedItems, EditAllItems, FolderContact, FolderVisible
Confirm
Are you sure you want to perform this action?
Removing Public Folder Permission on “\folder\sharedItems” for User “pic”, Access Rights “‘CreateItems’, ‘EditOwnedItems’, ‘EditAllItems’, ‘FolderContact’, ‘FolderVisible’”.
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help
(default is “Y”): y[PS] C:\Windows\System32>Add-PublicFolderClientPermission -Identity “\folder\sharedItems” -AccessRights author -User “pic”
Identity User AccessRights
——– —- ————
\folder\sharedItems swissitpro.ch/OU1/pic … {Author}
Adding the access rights of FolderContact simply identifies the account as the administrative contact for the public folder:
[PS] C:\Windows\System32>Add-PublicFolderClientPermission -Identity “\folder\sharedItems” -AccessRights FolderContact -User “pic”
The state of the public folder access rights for user pic now reads:
[PS] C:\Windows\System32>Get-PublicFolderClientPermission -Identity “\folder\sharedItems” | fl
…
Identity : \folder\sharedItems
User : swissitpro.ch/OU1/pic
AccessRights : {ReadItems, CreateItems, EditOwnedItems, DeleteOwnedItems, FolderContact, FolderVisible}…
Scenario B: Person-In-Charge cannot modify items created by others
So far, the modifications grant the pic user access rights to peruse the public folder, create, modify and delete objects owned by him/her only. S/he is not able to carry out his/her duties as PIC to administer items created by others in the same location.
To fix this, add the missing access rights with the end result as shown:
[PS] C:\Windows\System32>Add-PublicFolderClientPermission -Identity “\folder\sharedItems” -AccessRights EditAllItems,DeleteAllItems -User “pic”
[PS] C:\Windows\System32>Get-PublicFolderClientPermission -Identity “\folder\sharedItems” | fl
…
Identity : \folder\sharedItems
User : swissitpro.ch/OU1/pic
AccessRights : {ReadItems, CreateItems, EditOwnedItems, DeleteOwnedItems, EditAllItems, DeleteAllItems, FolderContact, FolderVisible}
<QueryList>
<Query Id="0" Path="Security">
<Select Path="Security">*[EventData[Data and (Data="swilkinson")]]</Select>
</Query>
</QueryList>
Here are examples of simple custom filters in Windows Event Log:
Select all events in the Security Event Log where the account name involved (TargetUserName) is "AUser"
<QueryList><Query Id="0" Path="Security"><Select Path="Security">*[EventData[Data[@Name="TargetUserName"] and (Data="AUser")]]</Select></Query></QueryList>
Select all events in the Security Event Log where the string "AUser" is present as data anywhere in the EventData section
<QueryList><Query Id="0" Path="Security"><Select Path="Security">*[EventData[Data and (Data="AUser")]]</Select></Query></QueryList>
Select all events in the Security Event Log where the strings "AUser" or "JDoe" are present as data anywhere in the EventData section
<QueryList><Query Id="0" Path="Security"><Select Path="Security">*[EventData[Data and (Data="AUser" or Data="JDoe")]]</Select></Query></QueryList>
Select all events in the Security Event Log where the string "AUser" is present as data anywhere in the EventData section and the Event ID is "4471"
<QueryList><Query Id="0" Path="Security"><Select Path="Security">*[System[(EventID="4771")]] and *[EventData[Data and (Data="AUser")]]</Select></Query></QueryList>
netdom resetpwd /s:server /ud:domain\User /pd:*
The /s:server is the name of another domain controller in which the KDC service is running. That server will be used for setting the machine account password.
The other two parameters are simply the user name and password for a domain administrator account.
You will need to install the Windows Server Support Tools from the CD-ROM. Once installed, you have to stop the Kerberos Key Distribution Center service and set the Startup Type to Manual.
Note that this method basically is fixing a problem with replication between two domain controllers. Sometimes replication can fail because the secret password between the domain controllers gets out of sync.
Make sure replication between your domain controllers is actually working!
You can use the Diskpart.exe utility to manage disks, partitions, and volumes from a command-line interface. You can use Diskpart.exe on both Basic disks and Dynamic disks. If an NTFS volume resides on a hardware RAID 5 container that can add space to the container, you can extend the NTFS Volume with Diskpart.exe while the disk remains a Basic disk.
Use the extend command to incorporate unallocated space into an existing volume while preserving the data.
The following are the requirements for the extend command:
To extend a partition or volume, you must first select the volume to give it the focus, and then you can specify how large to make the extension. To extend a volume, follow these steps:
disk=n
The dynamic disk on which to extend the volume. Space equal to size=n is allocated on the disk. If no disk is specified, the volume is extended on the current disk.
noerr
For scripting only. When an error is thrown, this parameter specifies that Diskpart continue to process commands as if the error did not occur. Without the noerr parameter, an error causes Diskpart to exit with an error code.
When the extend command is complete, you should receive a message that states that Diskpart successfully extended the volume. The new space should be added to the existing drive while maintaining the data on the volume.
Version: 6.0 and higher
Network Topology:
Two firewall interfaces configured in untrust zone. One for each internet service provider.
Description:
You can setup a second internet service as a configured backup line for use during failure on the primary line. This utilizes interface backup and the track-ip features of ScreenOS 6.
This will automatically do the failover during the outage. This example assumes that ethernet0/0 is the current primary interface while ethernet0/1 is the new service interface.
Configuration:
Setup the new service interface
Add the ip address and untrust zone to ethernet0/1 or setup the dhcp on this interface for the new carrier.
If this is a static configuration then add the second default route to the carrier provided address out ethernet0/1. On DHCP this route is added automatically.
Establish the backup and primary interfaces.
Web
Network–Interfaces–Backup
Select Primary interface ethernet0/0
Select Backup interface ethernet0/1
Select Track-ip
Hit Apply
CLI
set interface ethernet0/0 backup interface ethernet0/1 type track-ip
Setup Track-ip Monitoring to detect failure
Create the track-ip on interface ethernet0/0.
This is an internet ip address that when this interface can no longer ping it is considered down. A good choice is the service provider DNS server for this line.
Web
Network–Interfaces–List
Edit ethernet0/0
Monitor tab
Select enable track-ip
hit apply
Hit Add Monitor track ip
Enter ip address to ping (Carrier DNS)
CLI
set interface ethernet0/0 monitor track-ip ip
set interface ethernet0/0 monitor track-ip ip 1.1.1.1
Verification:
Look at interface list and observe that primary line is up and backup interface is down
Disconnect the primary interface cable and observe the change in status on the interfaces
References:
ScreenOS Concepts and Examples Guide
http://www.juniper.net/techpubs/software/screenos/
Volume 2 Fundamentals
Chapter 3 Interfaces
Configuring Backup Interfaces
Using the device status LEDs: 1. Locate the Reset (or Reset Config) pinhole on the device. Using a thin wire (such as a straightened paperclip), push the pinhole button for four to six seconds. The Status LED blinks red. NOTE: If you do not follow the complete sequence, the reset process cancels without any configuration change and the console message states that the erasure of the configuration is aborted. The Status LED returns to blinking green. The device generates SNMP and SYSLOG alerts to configured SNMP or SYSLOG trap hosts.Resetting the Device to Factory Defaults 41 Chapter 3: Configuring the Device 2. As soon as the Status LED blinks green, release the pinhole button and wait two seconds. 3. The device now waits for the second reset, which confirms the operation. Push the pinhole button again for four to six seconds until the device resets. The system now resets and returns to the login prompt; the default login name and password are both reset to netscreen.
A – PREWORK:
Run a Windows Update and install everything you can.
B – EXCHANGE 2010 CORE INSTALL:
Enter your PRODUCT KEY.
C – CONFIGURE EXCHANGE 2010 & MIGRATE YOUR DATA:
Now that the install is complete and tested, you need to perform some migration & configuration tasks:
D – MOVING AN EXCHANGE 2007 CERTIFICATE TO EXCHANGE 2010
I don’t enjoy dealing with certificates, so I buy multiyear certs and so my old 2007 Exchange server had a cert with more than a year left on it and I do not want to buy a new one! Below is how I moved it:
| NAME | EXAMPLE |
| external mail server name | mail.commodore.ca |
| autodiscover name | autodiscover.commodore.ca |
| root domain name | commodore.ca |
| internal fqdn of host | server1.corpdomain.local |
| host name | server1 |
From this section on I am going to talk about GoDaddy, because that is who I use and that is who I like. However, all other certificate providers will have a similar process.
To Install Intermediate Certificate Bundles
NOTE: Do not disable the Go Daddy Secure Certification Authority certificate located in the Intermediate Certification To Install the SSL Certificate on Microsoft Exchange 2010 – SEE MY SCREEN SHOT BELOW
|
E – POP3:
On the off chance you care about POP3, follow these three simple steps:
(Note, this is straight from my 2007 instructions so the screens look slightly different)
F – ANTISPAM
If you want to see how to install Forefront Protection 2010 for Exchange read my short instructions HERE, otherwise… read this:
You might be thinking to yourself, hey, I saw the ANTISPAM tab under ORGANIZATION, HUB TRANSPORT, and I even went so far as to check that the configuration from the old 2007 server had moved over… ya… but it will not fuction on the new server until you install it.
For more information see our AntiSpam section of our Exchange 2007 documentation (section D HERE).
G – QUICK CUSTOMIZE/BRAND OWA (Outlook Web App)
If you want to customize your OWA screens, all you have to do is change two graphics. Both are stored under the following path by default:
c:Program FilesMicrosoftExchange ServerV14ClientAccessOwa#current_numthemesBase
Just snap your corporate logo on to both lgntopl.gif and logoowa.png and save them in the BASE folder. This will be the default for all users as they log in.
Note that lgntopl.gif is also used by the log off screen so you kill two birds with one edit :).
The only problem with this process is that every notable Exchange patch will overwrite your changes so I created a folder called COPY TO BASE where I store these two graphics and I simply re-copy them into the BASE folder after every Exchange upgrade.
There is alot more customization you can perfom but I can not find much on 2010. However, nearly all of the 2007 customization instructions still apply. Sooo you can read THIS for more detail.
H – DECOMMISSION OLD EXCHANGE 2007 SINGLE SERVER
Once you are sure all has been moved to 2010, it is time to dump your 2007. So here is the process:
If you are worried about the process, watch THIS video or THIS Microsoft text (and yes, you can ignore the part where he says you should delete the old Exchange 2007 database before uninstalling… I have both done this and confirmed it with MS Tech Support.)
If for some reason your Exchange 2010 server still has references to the old server, you can removing the old server from the domain manually by following THESE instructions.
I – VERIFICATION:
After you have everything running to your satisfaction you should run a couple of simple and fast system checks:
and then you should run:
Test-SystemHealth
and make sure everything looks as you expect it should.
For the purposes of this article, I am assuming that the SBS server will be decommissioned at the end of the process, leaving a windows 2003 server Native Domain with a separate dedicated Domain Controller (DC) and separate server box running Exchange 2003 Standard.
You could in-fact keep the SBS server in the domain, so long as it remains a “god” in terms of holding the FSMO roles and being the DC in the root of the forest. Remember, you can’t have more than one SBS server in a forest at any one time!
This sounds easy, but do not forget that SBS is a control freak and wants to be in-charge of the whole forest. So asking it to take a back seat needs slow and careful attention. Disobey these rules at your peril. Plus, if you throw Exchange into the mix, this makes for quite a complex operation. Do not experiment on a live system. The slightest error and you lose the whole domain.
Figure 1: Test Lab Scenario setup
Figure 1 is a diagram of the lab environment that I have created for this tutorial using Virtual Server. SBS represents the original Small Business Server 2003 with Exchange installed and configured. DC01 will be the new domain controller and Exchange01 will be the new Exchange server. At the end of the process, SBS will be decommissioned, leaving DC01 controlling the domain and Exchange01 as the Exchange server.
To clear things up straight away, Microsoft does not permit you to separate components of SBS 2003, for example to install Exchange on another server. I have been asked this question on my blog previously.
The main steps of this procedure are as follows:
Firstly, change the network card settings of DC01 to point to SBS for DNS.
Figure 2: Internet Protocol settings
Then, right click My Computer and Click properties, then click the Computer Name tab.
Click the Change Button, and enter the details of the domain to join.
Figure 3: Joining the domain
Click OK. You will then be prompted to enter a Username and Password with the permissions necessary to join the domain. Enter the username and password and click OK. You will then need to reboot.
Go to Add Remove Programs, Add Remove Windows Components.
Select Network Services and click details.
Figure 4: Install Networking Services
Select DNS and WINS and click OK.
Click Start, Run. Then enter dcpromo and click OK.
Click through the Wizard then select Additional domain controller for an existing domain. Click Next.
Figure 5: Active Directory Installation
Enter a username and password with the permissions capable of doing this, e.g. Administrator. Click Next.
Enter the name of the domain (e.g. yellowpark.local) and click Next.
Select the location where you would like to store the database folder and the log folder, for the purpose of this article accept the defaults, Click Next.
Figure 6: Database and Log folders
Select the location you would like the Sysvol folder to be stored. Again, accept the default and click next.
Figure 7: Sysvol folder location
Enter a password to be used for the Directory Services Restore Mode. Make sure you don’t forget this! Click Nexttwice. DCPromo starts running and will take a few minutes to complete.
You will be prompted to reboot upon completion. Reboot and log onto the domain DC01.
Expand Sites, Expand Servers, then expand NTDS Settings. Right click NTDS Settings for Exchange01 and ClickProperties.
Tick Global Catalog.
Figure 8: Global Catalog Server
Click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
Click the change button to change the RID Master role to DC01. Repeat this for each of the other tabs.
Figure 9: Operations Master Roles
To transfer the Domain Naming Master, Open Active Directory Domains and Trusts.
Click Start, point to Administrative Tools, and then click Active Directory Domains and Trusts.
Right Click Active Directory Domains and Trusts Node and click Operations Master. Click the change button to change the Operations Master to DC01.
Figure 10: Domain Naming Master
To transfer the Schema Master role:
Firstly, you’ll need to register Schmmgmt.dll (if you haven’t used it before). Click Start, click Run, type regsvr32 schmmgmt.dll, and then click OK. Then create a new snap in. Click Start, click Run, type mmc, and then click OK.Right-click Active Directory Schema, and then click Change Domain Controller. Specify DC01. Right-click Active Directory Schema, and then click Operations Master. In the Change Schema Master dialog box, click Change. Move the site licensing server to the SBS 2003 computer. To do this, open Active Directory Sites and Services. Expand Sites and then click Default-First-Site-Name. Right-click Licensing Site Settings, and then clickProperties. Click Change, type the name of DC01 in the Enter the object name to select area, and then click OK.
It can take an hour for this event to show. I usually go and make a cup of tea and come back later. There is a work around to make it happen quicker, but I would avoid it. When I did this test lab, it took 1 hour 47 minutes before I saw Event 1869.
In Part 1, I covered the main steps required to prepare the forest, domain and network for decommissioning Small Business Server 2003 (SBS) from a forest. In this article I will cover the steps necessary to move Exchange from SBS to a different server and decommission SBS from the network.
At this point, we should have a new domain controller (DC01) installed into the domain. This is also a GC and holds all the FSMO roles. Next up, we will join Exchange01 to the domain and install Exchange 2003 onto Exchange01.
I’m not going to run through the installation process. Suffice to say, for the purposes of this tutorial, I have accepted the installation defaults. You can find a good article on the msexchange.org website for best practices on installing Exchange Server 2003.
Make sure you use Netdiag and Dcdiag to test all your network settings and connections. Also use these if you run into problems. It will instantly tell you what’s going wrong on the network.
You might also want to throw in gpupdate /force to check that the domain is refreshing policies OK. This checks if user permissions are running as expected and everything can talk to each other.
During this next stage, we will accomplish the following tasks:
Open Exchange System Manager and check that the SBS and Exchange01 are showing as servers in the organisation.
Firstly, you want to replicate all the Public Folders on to Exchange01. This will then give you two copies of your public folders, which is good working practice anyway.
Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
If the Display administrative groups option is turned on, expand Administrative Groups, and then expand First Administrative Group. (To display administrative groups, right-click Your_Organization, click Properties, click to select the Display administrative groups check box, click OK two times, and then restart Exchange System Manager).
Figure 2: Display Administrative Groups
Expand Folders, expand Public Folders, right-click a top-level public folder, and then click Properties.
Click the Replication tab, and then click Add.
Figure 3: Public Folder Replication
In the Select a Public Store box, select the name of the server where you want a replica of this public folder (Exchange01), and then click OK.
Click Apply, and then click OK. If this public folder has any subfolders and if you want these subfolders to have a replica on the destination server, right-click the top-level public folder, click All Tasks, and then click Manage Settings.
In the Propagate Folder Settings box, click to select the Replicas check box, and then click OK. When you complete this step, all subfolders of that top-level folder have a replica on the destination server.
Repeat steps 1 to 7 for all the Public Folders.
Next you need to wait for replication again, and then check that the public folders are In Sync. Follow these steps:
Figure 4: Public Folders In Sync
Next you must turn off replication for each public folder. To do this, follow these steps:
You must designate Exchange01 to be the routing group master. To do this, follow these steps:
In Exchange System Manager, expand First Administrative Group (where First Administrative Group is the name of your administrative group), expand Routing Groups, and then expand First Routing Group (where First Routing Group is the name of the routing group where you want to change the routing group master).
Click Members, right-click the server in the right pane that you want to make the routing group master, and then clickSet as Master.
Figure 5: Routing Group Master
Create another Site Replication Service (SRS) instance
If you have Site Replication Service (SRS) installed and running, you must create a new SRS in Exchange System Manager. I’m leaving this out, as we are assuming the SBS Server was a stand alone system.
Set-up connectors on Exchange01
Next you need to set-up any connectors from SBS on Exchange01. To do this, simply write down the connector settings from SBS and recreate them on Exchange01.
Move mailboxes to Exchange01
To transfer mailboxes from SBS to Exchange01, follow these steps:
Open Exchange System Manager and drill down to the Mailbox Store on SBS.
In the right pane, select the mailboxes you wish to move by holding down the Ctrl key and selecting the mailboxes with the mouse. Then right click, and click Exchange Tasks. Click Next on the Exchange Task Wizard.
On the Available Tasks page, under Select a task to perform, click Move Mailbox, and then click Next.
On the Move Mailbox page, click the destination server that is in the Server list, click a mailbox store in the Mailbox Store list, and then click Next.
Configure how to handle corrupted messages that are found during the move, and click Next two times.
Some mailboxes might take a couple of goes to transfer over. This is normal. Get as many done en-mass, then correct the errors.
After you have transferred mailboxes to the new server, the final stage of the process is to uninstall Exchange from SBS, dcpromo down to a member server, then remove SBS from the domain.
To uninstall Exchange Server from SBS, go to Control Panel and double click Add or Remove Programmes.
Select Windows Small Business Server from the list of programmes and click Change/Remove. Click through the wizard until your reach the components selection page.
In the Action column, select Remove from the drop down list. Click Next twice. Exchange will then be unistalled from the server.
Figure 6: Uninstall Exchange from SBS
When the uninstall has completed, reboot. Then run dcpromo. To do this, Click Start, Run, type dcpromo and clickOK. Following this process the SBS will be a member server in the domain.
To remove SBS from the domain, right click MyComputer and select properties. Click the Computer Name tab and click the Workgroup radio button. Enter WORKGROUP for the new workgroup name and click OK. You will be prompted to reboot.
Following this, your new network will be running with a Stand alone Domain Controller (DC01) and stand alone Exchange Server (Exchange01).
This is a relatively straight-forward process so long as you take your time, and you’ve tried it out before. Do not experiment on a live system. When I did this for real the first time, I had a test network set-up that I used to try all the steps first. You could use Virtual server for this.
