vWorld.nl
Because it's a virtual world!
Because it's a virtual world!
Oct 19th
Today a customer complained about the SBS console not completely working. The administrator’s account received an error no “rights for exchange”.
Although the user was a member of all the correct groups, the solution was simple. The domain admin account’s primary group membership was domain admins and should be domain users. Now everything is working fine!
Oct 18th
Before I upgrade a domain I usually check for problems and issues. I use the following steps to give me an idea of the status :
dcdiag /v
(Check DC en services)
netdiag /v
Check networking components
netsh dhcp show server
Show DHCP status
repadmin /showreps
Show all replication between sites
repadmin /replsum /errorsonly
Show replication issues
When you perform the steps mentioned and you didn’t ran into several errors than you have probably nothing to worry about.
Oct 13th
I ran into a problem with VMware converter. I got the following error :
unable to create a VSS snapshot of the source volume(s). Error code: 2147754774
The following steps worked for me :
Confirm that there are no errors with the following command :
vssadmin list writers
I found more then one provider with the following command :
vssadmin list providers
I deleted the second (everything but the first) provider (please back-up your keys first!) :
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers
I then did a restart of the VSS service (net stop vss , net start vss)
Followed by enabling shadow copies (and made a snapshot of the drive)
Now I was able to succesfully create VSS and import a running physical machine using VMware converter!
Sep 15th
This is how you do that :
Connect to the switch with the serial cable and putty.
Login with the credentials recover / recover
Reset the switch (power down, power on) within 30 secs
Now you can re-configure your switch with all the necessary accounts like admin/manager/monitor/security
You can even disable the recover possibility, hope you didn’t do that because then these steps won’t work.
Sep 12th
Today when troubleshooting Activesync problems with an Exchange 2007 environment I decided to delete en re-create the Exchange Activesync virtual directory. I used the following steps :
This is often a clean and fast solution when several options has been altered for troubleshooting for example.
Sep 6th
I found the sollution for the following error :
The solution was to specify the right DNS servers in the DNS console.
Open the Microsft Exchange Management Console
Select properties of the hub transport or the EDGE server.
Make sure that the right DNS servers are specified by internal and external DNS lookups.
Finally restart the Microsoft Exchange Transport services and check out the application log.
Jul 15th
Everybody has seen it one or twice. When importing exchange data using PST files that a user has both an postvak in as an inbox folder.
I found a nifty tool that changes the language of the exchange mailbox to a specified language.
For example :
As you can see the above mailbox language is in English.
Now you start the tool (ignore the mapi error) and select the user(s) you wish to change :
You hit set and you will notice the mailbox(es) are changed into the preferred language :
You can download the software here. The software is made by a company called amrein. Visit them at http://www.amrein.com
Jul 14th
A customer had problems synchronizing large amount of data to an EMC CIFS share using the robocopy /mir commandline option.
2011/07/14 13:38:58 ERROR 112 (0x00000070) Creating Destination Directory \\xxxx\xxx\ There is not enough space on the disk. Waiting 30 seconds...
After some troubleshooting I found that opslock, hidden sharing and CIFS caching were not the problem but the fact that the share was thin created. I created 2 shares, one thin and one fat. You guessed it right, the thin version failed. Changed the properties to fat and the problem was gone!