A lot of times when you are busy doing a mailbox move you will see that the transaction logs can actually grow just as big as the size of the Database. So what can happen is you can run out of space on your database drive and the mailbox move will stop.
To work around this issue you can temporarily enable Circular Logging that will keep deleting the transaction logs while the mailbox move in progress.
To achieve this do the following:
1. Open Exchange Management Console – Go to Organisation – Mailbox
2. Select the Mailbox Database you are performing the move on. Right click – Properties
3. Enable Circular Logging
4. Restart the information Store Service for changes to take affect. (Please note this will temporarily disconnect your users)
After this please be sure to enable it as the Transaction logs assist in recovery situations.
After you have migrated your terminal servers or configured Session Broker with roaming profiles you might find that some users are being logged in with temporary profiles. Below describes the steps to resolve this.
- Request the user to log off from the TS session.
- Log in as the user and detect if the profile is problematic – It should give you a pop up telling you that you are logged in with a temp profile. To make sure, open command prompt and see if it shows the correct users profile in the first line or if it shows a temp profile.
- If you are using Session Broker (High availability terminal servers) – Go to command prompt, type hostname and see on what server you are experiencing the temp profile issue for the specific user (The problem might only be on the specific terminal server).
- Log off as the user and log on with an admin account.
- Go to regedit, locate the user and delete the users profile registry key.
HK_LOCAL_ MACHINE -> Software -> Microsoft -> Windows NT -> CurrentVersion -> ProfileList.
Right-click on ‘ProfileList’, click on ‘find’, type the name of the user, you will be directed to the users registery key, delete it (if there’s a duplicate, delete both). It usually creates a .bak registry entry if the profile is problematic.
6. Copy the users pofile to a backup location (Moving the users profile out of the roaming profile location).
6. You can now log in as the user – It will create a new profile for the user.
7. Copy the old profile’s data to the new profile.
The user should now be able to continue working without being logged in with a temp profile.
For server 2008 Terminal Servers you can use Easy Print – You don’t need identical drivers on Server and client.
For server 2003 Terminal Server you would need identical drivers on Server and client.
For Easy Print to work on Windows XP machines you would need SP3 and .Net Framework 3.5 installed.
Make sure ‘printers’ are selected on local resources of clients DRP connection.
I always struggle to find a straight forward command for getting Mailbox sizes in Exchange 2010. Although there is a lot of information out there, they all seem to over complicate things and don’t just give you what you require.
This is all you need:
Get-MailboxStatistics -Database “Mailbox Database*” | Select DisplayName, ItemCount, TotalItemSize | Sort-Object TotalItemSize -Descending | Export-CSV C:\MailBoxSizes.csv
This command will get the mailboxes sizes for all Databases beginning with Mailbox Database, Sort them according to size and export to a csv file.
I picked up a strange issue with a Win 7 64bit laptop that could not browse at all. I checked all the network settings and was able to resolve DNS as well as ping websites. What was even stranger was that after installing Firefox I could not browse using that either.
After struggling for more than an hour I tried the 64 bit version of Internet Explorer and browsing was working.
After much research and trying every possible option like browser reset and even uninstalling IE 9. I found the following commands which solved the problem:
netsh winsock reset catalog
netsh int ip reset reset.log hit
I assume it was a Adobe Reader update that caused it as the client told me Adobe asked him to update and after that he computer just hanged. That is when the problem occurred.
I once got the below message when trying to remote to a server after removing Active Directory from a server using dcpromo.
The reason I got the error message was because the server was configured to look at itself as a DNS server and because the DNS was also removed with the DCpromo command it could not find an Active Directory server for authentication.
The workaround I found was to add the following Dword to the registry:
In the folder:
Add the following key:
This will allow you to remotely log into the server. Just take note that it might take a while for the first logon to go through.
Below are the steps for exporting all mailboxes to PST’s.
You can’t run the export from a 64bit OS.
Below describes the steps:
1. Find a server/PC with a 32bit OS.
2. Install the Exchange Management Tools (Exchange 2007 SP1 or later) – You can install this from the Exchange Media.
3. Install Outlook 2003 (SP2 or later).
4. From the Exchange Management Shell run the following command:
get-mailbox -server “Your server name” | export-mailbox -PSTfolderPath “Folder Path”
This will export all mailboxes to PST’s. It won’t remove any data from the mailboxes, it will just make a copy to the PST’s.
If if re-run the export it will merge the mails into the PST’s.
One problem I came across while trying to do the export was an error due to insufficient access rights on the mailboxes. Below is the error I received:
Error was found for ‘User’ because: Error occurred in the step: Moving messages. Failed to copy messages to the destination mailbox store with error: MAPI or an inspecified service provider.
To resolve this run the following command:
Get-Mailbox -Server “Server name” | Add-MailboxPermission -user “User with which you run the Export command” -AccessRights FullAccess
As you know when doing any sort of Server migration like Small Business server it is always best practice to remove the ISA Server as it can cause problems with moving mailboxes.
When trying to move the mailbox you might get the following error.
MapiExceptionNetworkError: Unable to make connection to the server.
To resolve this you need to uninstall ISA and then try the move again. Problem is sometimes when trying to uninstall ISA you will get the following error:
This patch package could not be opened. Verify that the patch package exists and that you can access it or contact the application vendor to verify that this is a valid Windows Installer Patch package.
I have found 2 different solutions to resolving this problem:
1. Run the Microsoft’s Fix problems with programs that can’t be installed or uninstalled which can be found here:
When running you will select ISA from the list and even thou the Tool says that it could not repair ISA you will still be able to completely uninstall it.
Unfortunately this tool sometimes give the following error message when trying to run it on a Small Business Server.
This troubleshooter does not apply to your system
We’re sorry, but this troubleshooter is not compatible with your current system’s configuration.
2. What I did to get around this problem was download and install ISA 2004 Service Pack 3 from the link below and re-apply it. After that I was able to uninstall ISA completely.
Link to ISA SP3: http://www.microsoft.com/en-us/download/details.aspx?id=8836
So you’ve installed your new Exchange 2010 server but now you have to change your printers to point to the new server otherwise the scan to email is going to stop working when you decommission the old server.
Here is the steps you need to follow;
This connector will be an Internal SMTP relay connector that does not require authentication for the specified IP addresses.
- Open you Exchange Management Console and go to: Server Configuration – Hub Transport
- Right Click and select – New Receive Connector
- Give your connector a name and select Custom under intended use.
- Under Local network settings leave as default and click next
- This is the part that caused my relay connector to never work. By default any IP address is allowed to relay. Remove this and only add the printers’ specific IP addresses. So it will be for example: 192.168.0.1/32 If you add the entire subnet for example 192.168.0.0/24 then the connector will not work as the default connector will then take precedence which requires authentication.
- Click new and the connector will be created
- Then right-click on the newly created connector and select properties.
- Go to the Permission Groups tab and tick Anonymous users and Exchange servers
- Go to the Authentication tab and tick the Externally Secured box.
- Then just change the printers to point to the IP address of the new server.
- One consideration if you have Anti-spam enabled on the exchange server then you just have to white list the printers so it doesn’t get blocked as spam.
I took me a while to figure out how to Deploy printers affectively using Group Policy.
Below is a step by step guide on how to deploy it for computers running Win XP and upwards.
- Download the appropriate drivers for the printer. This will mean in most cases you will need the 64 and 32bit drivers. I usually download the drivers for Server 2008 32 and 2008 64 as this seems to work the best.
- Install the Print Server role which can be found under Print & Document Services
- Open the Print Management MMC and go to the server. Right click and add the network printer exactly like you would normally.
- After its finished install right click on the printer go to Properties – Sharing – Additional Drivers and add the 32 bit drivers.
- Open the Group policy Management Console and create a Group Policy Object Called Deployed Printers. After this you have to link it either to an Organisational Unit on straight to the domain. When linking it to a OU please take note that you can deploy the printer per user or per computer. So make sure the if you deploy per user that the OU contains Users.
- Right click on the printer and select Deploy Printer with Group policy.
- Browse and select the Group Policy we created in step 5 and tick the users box. Then click add to deploy the printer. Your printer will then be listed under Deployed printers. The printer will then be available after a restart for workstations Vista and upwards. For computer running Win XP please continue with step 8.
- With Win XP computers we also need to add a file called Pushprinterconnections.exe which I’ve uploaded as I struggled to get hold of it.
- Edit the Deployed Printers Group policy and go to User Configuration – Policies – Windows Settings – Scripts and edit the Logon Scripts.
- Click on show files and copy the pushprinterconnections.exe into that folder. Then close the folder.
- Click add and select the pushprinterconnections.exe file and click ok.
- Apply and close the Policy and your XP computer should now also have the printer applied after a restart.