Monday, 29 July 2013

A user was trying to log in to their computer but was getting a message saying that they were being logged in with a temporary profile. Deleting the users profile did not make any difference.In order to fix the problem, a change had to be made to the registry.1. Login as admin and backup the users profile in C:\Users\Username2. Go to HKEY_LOCAL_MACHINE > Software > Microsoft > Windows NT > Current Version > Profile List3. Find the SID.bak for the user's profile (click on the "folder" and the path to the profile should be listed)4. Delete the SID.bak5. Login as the user to recreate the profile. Log off and back in as admin and copy their backed up files across

Friday, 12 July 2013

When backing up a VM using Veeam Backup and Replication, I kept seeing the message;

Hot add is not supported for this disk, failing over to network mode...

This was occurring because the LUN that my Veeam proxy server was running on was formatted in VMFS-3, whilst the server I was trying to back up was on a LUN running VMFS-5 and had a different block size.After upgrading the proxy LUN to VMFS-5, disks began hot-adding successfully.

After migrating to Exchange 2010 from 2003, I found that Microsoft had removed the "Set As Primary" button from the E-mail Addresses tab in Active Directory. In order to change the primary address I had to follow the steps below;

1. Login to the new Exchange server and open Exchange Management Console

Tuesday, 9 July 2013

When attempting to delete email in the setup below, users received a popup stating "Unknown Error" and could not delete the mail. Selecting the mail and trying to delete again sometimes allowed the deletion to occur.Users were on a Terminal Server running Windows Server 2003 R2 (SP2) and were using Outlook 2003 (SP3). The Exchange server had recently been migrated to Exchange 2010 (SP1).The problem was resolved by updating Exchange 2010 to SP3.

Wednesday, 3 July 2013

It is possible to list all snapshots on a Nexenta device, as well as remove them via the command line. To do this, follow the commands below;1. SSH as ADMIN onto the device you are replicating to.2. SU to root permissions, but don't enter nmc. Your path should read something like root@devicename:/export/home/admin#3. Run the command;

zfs list -t snapshot

This will list all snapshots on the device. The more snaps you have, the longer this will take so go make a cup of tea while it is running.4. Find the name of the snap you wish to remove and run the command;

zfs destroy snapname

You can also remove snapshots through the Nexenta GUI by navigating to Data Management > Data Sets > Snapshots

When trying to set up a new Auto-Sync service I was encountering an error telling me that there was not enough space to replicate the LUN, despite there being 50% free space on the device.After looking at the free space, it appears that each folder on a Nexenta device has a hard size limit of 5TB.I created a new folder and attempted to recreate the auto-sync and the service created and ran successfully.To view the current space used in a folder follow the instructions below;1. SSH as ADMIN onto the device you are replicating to.2. SU to root permissions, but don't enter nmc. Your path should read something like root@devicename:/export/home/admin#3. Run the command;