AI Adsense

Thursday, August 29, 2013

Removing Exchange 2007 Public Folders from Exchange 2010 Environment

Before beginning any of this work make sure you either no longer need public folders in your environment (Office 2000/2003 has to have them) or that they have fully replicated to your new Exchange server.

1. Try to remove the public folders through the EMC.  If this fails now it's time to get tough.

2. Open Exchange Management Shell and enter the following:

Get-PublicFolder -Server SERVERNAME "\" -Recurse -ResultSize:Unlimited | Remove-PublicFolder -Server SERVERNAME -Recurse -ErrorAction:SilentlyContinue
3. Next run this command:
Get-PublicFolder -Server SERVERNAME "\Non_Ipm_Subtree" -Recurse -ResultSize:Unlimited | Remove-PublicFolder -Server SERVERNAME -Recurse -ErrorAction:SilentlyContinue
4. Refresh the EMC and the public folders will be gone.  If this does not work and you're fully sure you need them removed then this last step truly removes them from the environment.  All that's left is to manually delete the files if needed.

  1. Connect to your DC.
  2. Open ADSIEDIT.MSC console and connect to configuration.
  3. Go to the following path.
–> CN=Configuration –> CN=Services –> CN=Microsoft Exchange –> CN=YOUR ORGANISATION –> CN=Administrative Groups –> CN=First Administrative Group –> CN=Servers –> CN=SERVER NAME +—> CN=InformationStore

This final step ensures that even though the folders/files may still exist they are removed from AD and will not prevent removing Exchange 2007 at that point.

Good luck! 

Wednesday, August 28, 2013

FOG server error "host unreachable" when trying to upload an image

Tonight I'm doing some imaging of HP tablets and upgrading them from Windows XP to Windows 7.  This is a new FOG installation and I just ran into this error.  Here's the fix:

No matter what you named the FOG server on your network, make sure you have a DNS entry on your DNS server that DHCP is pointing to and create an A record named "fogserver" minus the quotes of course.

Once you do that then restart the machine you want to push the image of to your FOG server.  Problem solved and it will upload after that.  On a 100M switch you can expect about 1.4 to 1.5G/min so the average new image runs about 20-25 minutes to upload.  Obviously gig switches are much faster provided your backend can keep up.

Good luck.

Tuesday, August 27, 2013

Installing VMware Tools on Ubuntu or Ubuntu Server

Ubuntu or Ubuntu Server with a Graphical User Interface

To mount the CD image and extract the contents:
  1. Power on the virtual machine.
  2. Log into the virtual machine using an account with administrator or root privileges.
  3. Go to Virtual Machine > Install VMware Tools (or VM > Install VMware Tools)..

    Note: If you are running the light version of Fusion, a version of Workstation without VMware Tools, or VMware Player, you are prompted to download Tools before they can be installed. Click Download Now to begin the download.
  4. Open the VMware Tools CD mounted on the Ubuntu desktop.
  5. Right-click the file name that is similar to VMwareTools.x.x.x-xxxx.tar.gz, click Extract to, and select the Ubuntu Desktop to save the extracted contents.

    The vmware-tools-distrib folder is extracted to the Ubuntu Desktop.
To install VMware Tools in Ubuntu:
  1. Open a Terminal windows.
  2. In Terminal, run this command to navigate to the vmware-tools-distrib folder:

    cd Desktop/vmware-tools-distrib
  3. Run this command to install VMware Tools:

    sudo ./ -d

    Note: The -d switch assumes that you want to accept the defaults. If you do not use -d, press Return to accept the defaults or supply your own answers.
  4. Enter your Ubuntu password.
  5. Restart the Ubuntu virtual machine after the VMware Tools installation completes.

Saturday, August 17, 2013

"Active Directory Replication is taking longer than expected" message stops SBS installation

SBS 2008 Event ID 13552 and 13555

Today I'm working a migration from SBS 2008 to SBS 2011.  This error came up.  In order to apply a fix I had to do some digging to get rid of this error.  The new SBS 2011 VM could not become a domain controller until this was fixed so here's what I have done.

Once this process is done then click Yes on the prompt from the new SBS server.  Replication will successfully complete and the setup of SBS 2011 will continue.

- Performing an authoritative restore:

1) Click Start, click Run, type cmd, and then click OK.
2) At the command prompt, type the following command, and then press ENTER:
net stop ntfrs
3) Click Start -> Run, type regedit, and then click OK.
4) Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
5) Right-click the BurFlags entry, and then click Modify.
6) In the Value data box, type D4 and then click OK, on the File menu, click Exit.
7) At the command prompt, type the following command, and then press ENTER:
 net start ntfrs


Thursday, August 01, 2013

dcpromo demote Win2k3 server Failed to configure the service NETLOGON as requested

Here's the full text of the error received:

the operation failed because:

Failed to configure the service NETLOGON as requested.
"The wait operation timed out"

and in the dcpromo.log is the following:

07/07 09:02:24 [INFO] Informed NETLOGON to deregister records
07/07 09:02:24 [INFO] Stopping service NETLOGON

07/07 09:04:24 [INFO] StopService on NETLOGON failed with 258

 To fix:

Change the first DNS setting on your network card to point to your new DNS server, not the server you are currently demoting.  Once you change the DNS setting to the new DNS server you will be able to demote the server without this issue.