Archive for the ‘Trend Micro’ Category


Guess I am like the cobbler’s kids who didn’t get their shoes when everyone else did.  I am the last of my clients, save one, to migrate off SBS and onto Windows 2012 R2 Standard.  I thought you could benefit from some of the issues I ran into, and solved.

Here’s my scenario.  Have a Hyper-V server running SBS 2011 as a virtual machine.  Created a new virtual machine and installed Windows 2012 R2, did updates.  Unfortunately, it sat for several months while I finally got a few days to do he migration.  More about that later.

Long ago, I migrated email and SharePoint to Office 365, so I had disabled services and IIS application pools on SBS.  My starting point was to fire them up again in order to remove them.  I did not want AD to migrate with all of those extra objects.

Removing Exchange Server 2008 R2

This did not start off well.  When I launched EMC, it failed to connect to the SBS server.  I ended up putting it aside for a few days but came back to it.  I had tried to guess or remember which services should be started, but I seemed to have failed.  I also only started the Exchange-related application pools.  I easily tracked down an article describing which services start automatically, fired them up, and enabled those that should start manually.  BTW it describes all of SBS services.

That did the trick, and EMC successfully opened.  But I knew that in order to uninstall Exchange, I had to remove the mailboxes.  Fortunately, I had a small number of them.  And to make it easy, I used Exchange PowerShell commands to do this.

Get-Mailbox | Disable-Mailbox
Get-Mailbox -Archive | Disable-Mailbox -Archive
Get-Mailbox -Arbitration | Disable-Mailbox -Arbitration

First, please note that my scenario had with SBS – a single mailbox database and server.  That is why there are no qualifying parameters on the commands.

If your first thought is to use EMC to remove mailboxes, CAUTION!  That method removes both the mailbox AND the user from AD.  If you do want to remove some users and their mailboxes, do that but otherwise use Disable-Mailbox.  There is a Remove-Mailbox command but it also removes both user and mailbox.

So what the first command does is get a list of mailboxes which are piped to the next command.  The second does the same thing but gets the archive mailboxes.  You will then not be surprised the third command gets the arbitration ones.

I tried just getting archive and arbitration mailboxes, but the id names were too long to display in their entirety, so piping was essential.  And easier. And faster.

I then tried to uninstall Exchange but got two failures.  The first block came from Trend Micro Worry Free Advanced that it was using the database and the second was the Offline Address Book in Public Folders.  I uninstalled the messaging agent for Trend Micro but getting rid of the OAB was harder.

First I tried to simply delete the public database but it was not empty (I knew that from the OAB warnings).  I then tried to create a new, empty one to mount but then Exchange would not let me create a second one.  So under Tools, I chose Public Folders and expanded the tree and selected OAB then the firs entry and deleted that.  It was the only entry I could delete.

Luckily, I was then able to uninstall Exchange.

Removing SharePoint

Could not have been easier.  Just uninstall from Control Panel.

Back to Windows 2012 R2

I had already joined the domain and installed Active Directory Services, so I was ready to promote it to a domain controller by starting the configuration on that role.  Just added to the existing domain and it just worked.

I needed a few more roles on this new server, and then trouble started.  I tried to add both Remote Access and Windows Update at the same time and the installation failed.  Separately they also failed.  Again and again.

I cheeked for updates and found plenty and installed and rebooted.  Still no luck in adding roles or features.  I finally found this article which pointed me to a fix.  Note that I modified both policies that it refers to.  After the gpupdate, installation of roles worked fine.

I had not run into this issue before with 2012 R2, so I think it is related to both the GPO settings from SBS 2011 and that AD is at 2008 R2 levels and cannot be promoted until SBS is removed from the domain.

But this puts me well on my way to being where I want to be.

Now I just have to move Worry Free Advanced and get client machines set up under Windows Essentials role.


The Scenario

I needed a Windows 7 OS to run an older version of an application on 32-bit, but I had converted my system to Windows 8 64-bit.  Since I had plenty of memory, I decided to run Windows 7 32-bit as a virtual machine using Hyper-v in Windows 8.  Since it is just like Hyper-v in Windows Server 2012, this was effortless.  I created the machine, installed Windows 7 32-bit on it, installed Office (needed for the app) and the app itself.

All was pretty heavenly, just clicked on the taskbar icon for the VM, and the app was at my fingertips.

Then something went wrong.  The data files could not be located on a network share.  It wasn’t the share but the whacky behavior of the network adapter on the virtual machine.  It could get a DHCP address from the server (release and renew worked), but it was otherwise isolated.  Kaput.  Couldn’t get to a thing.

First Attempt to Remedy

My thought was that the network adapter attached to the VM was faulty.  I could ping, but I either got destination not reachable or request timed out, often a mix of the two.  So I shut down the machine, went to settings, removed the network adapter and tried to add another one.  No luck.  It kept giving me a failure that it couldn’t add anything in the machine’s current state.

Tried to Create a New Virtual Machine

This seemed to indicate a problem with the instance of the virtual machine, and if I couldn’t remove devices, maybe I could use the existing .vhdx in a new machine.  I also decided to be clever and store it on a network share that was being backed up by Windows Server Backup.  Well, not so clever.  It wouldn’t allow me to stash the virtual machine there nor allow me to use the .vhdx copy I had placed there.  So back to storing om local drives.

But creating the virtual machine kept failing with an error that contained

“The requested operation cannot be performed on a file with user-mapped section open”

What the heck was that?  After some snooping, I realized it might be a permissions or blocking error.  Eliminating permissions, I decided to try and eliminate blocking. I had Trend Micro Worry Free Advanced running on the domain server, with an agent on this desktop, so I disabled it.

Sure enough, creating the virtual machine using the old .vhdx from the failed machine worked. And when it started, all was well with the network.

What I Learned

  1. You can re-use a virtual disk from an old virtual machine on a new virtual machine.
  2. Anti-virus software can block virtual machine creation and maybe ongoing operation.
  3. I needed material for a new post.

I hope this helps some of you expand your virtual Hype4r-v horizons.  It is a great tool.