Windows 2003 sbs vmware

Or do I need to manually configure additional disks? What about other interfaces, e. Which vmware files file types are necessary mandatory for the re-start in virtual box - should I delete all other files of the vm? Regards ennogrue. You do not have the required permissions to view the files attached to this post. Re: Migrating Windows SBS from vmware by ennogrue » Wed Feb 06, pm With APIC enabled and the disk as the first and only boot device the SBS indeed starts up for a few seconds showing the Windows start screen, but then shows a bluescreen telling Windows was shut down for security reasons, the disks should be checked and checkdisk be run.

The interesting thing is: In an eternal loop it starts again, again bluescreen and so on. Does this give a hint to the next problem? If there is the Windows screen shown it means it at least started to access and read from the system disk one of the disks. Again I attach the VBox.

You can try setting it to MB and see if it works better although it would be slow to boot. Also did you remember to remove the VMware guest additions? BSOD usually indicates a driver issue. Re: Migrating Windows SBS from vmware by mpack » Thu Feb 07, am Showing us the log is not really diagnostic for a bluescreen event, you need to tell us what the stop code is, or post a picture of it.

The Expert of the Year award recognizes an expert who helped improve Experts Exchange in the past year through high levels of contributions and participation on site. This award is given to the expert who has achieved the highest levels of participation, while maintaining quality contributions and professionalism.

What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange. All rights reserved. Covered by US Patent. Come for the solution, stay for everything else. Welcome to our community! Those run fine.

Since you are losing time I lost 1 sec for every 2 secs the time between cron jobs isnt exactly a minute, in my case it was 1. You are trying to use a time based tool cron to fix a time loss issue, which isn't going to work well. Basically, the OS running inside the VM is not getting timer-ticks during the time it's not actively scheduled, and so it doesn't know how much time has passed.

How to install the tools is slightly different for every guest OS, but almost always starts with choosing "Install VMWare Tools" or something like that from the VMWare console, which will mount a cd iso into the VMs cdrom with the tools on it.

For linux there is both an RPM and a tarball of the tools - windows guests that CD will autorun and start the tools install. I used to do the NTP thing every minute but let's face it it's an ugly solution. There is a sure fire way to resolve it which I have done , which is to recompile the kernel with a lower timer interrupt rate.

Recompiling the kernel is the silver bullet - I'd recommend going straight to it. All MS says is a product can support virtualization or it can't. So, as long as you have a product and role that is supported under virtualizatoin, and you are running a certified virtualizatoin platform, you are supported.

For example, Exchange's Unified Messaging role is not supported under virtualization. Doesn't matter if you are on SBS, standalone, or some other configuration, if you enable that role while virtualized Hyper-V, VMWare, doesn't matter , you are now in an unsupported state.

So plan carefully. I'm not sure it is supported as a guest with VMware, but there are certainly people who have installed it successfully. Thanks in advance Dana. I was not able to read the response at Experts Exchange so not sure what it says. We are going forward with Vmware but should would like something to show my boss to backup my statements to him.