Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

MOSS VMs, WS2008, AD

  Asked By: Vanraj    Date: Jan 21    Category: MOSS    Views: 902

I am interested in setting up MOSS on a VM that is running WS2008
x64. In addition to that, I would like to create a WS2003 VM that would
act as a domain controller for the MOSS WS2008 VM.

Anyone out there know if someone has created this type of virtual
environment before, or better yet if there are some VMs that others have
created that maybe I can leverage.

I am running VMWare Workstation.

Share: 

 

8 Answers Found

 
Answer #1    Answered By: Richard Allen     Answered On: Jan 21

We are starting to build a VM infrastructure for MOSS but haven't
installed MOSS yet. However, there is a problem with building domain
controllers on VMs. Perhaps you know this already but the big problem is
time - a VM's clock will drift away from the correct time fairly
quickly. Someone at a presentation I went to recently said they had
noticed a loss of about 17 minutes roughly every 24 hours. A domain
controller that is more than 5 minutes different from other DCs on the
domain will stop talking to them. The good news is that there are a
number of ways of dealing with this. One suggestion I saw was to make
the DC that runs the PDC emulator a physical server and set it up to use
a good source of time. Then make all the other DCs on the VMs use that
as the time source. I think it was also mentioned that you shouldn't
install VMWare tools on the DCs as that affects how the clock is synced.
I don't know why they suggested using the physical server for the DC
that acts as the primary time source. I would have thought a VM could do
this as well since it will be synced with a reliable time source located
elsewhere. Apologies if you knew this already. It was new to me at the
presentation I went to a few weeks ago.

 
Answer #2    Answered By: Ian Davis     Answered On: Jan 21

I have not worked with VMWare for some time, but I find the whole clock
drift issue interesting. Both Virtual Server and Virtual PC pull their time
for the virtual machines directly from the host system. Any drift is due
strictly to the drift of the host, which is pulling it's time from the DC.

Bear in mind, however, that Microsoft doesn't support running  Domain
Controllers within a non-Microsoft virtual environment. If you should have
an issue with your virtualized DC, you may be required by MS support to
replicate the problem on actual hardware prior to getting any support.

 
Answer #3    Answered By: Jagjit Hui     Answered On: Jan 21

Time drift would be a big problem if Kerberos is in use. I
found this link communities.vmware.com/thread/135137?tstart=45
which has some other links which, to be honest, I haven't followed but
they may be interesting. This one sets out a way of setting  things up so
that time will be right on DCs or at the very worst if it does drift
they all drift by the same amount. On reading it again I think he is
setting up the PDC on bare metal for other reasons and not because it is
the time server. I guess you could put all your DCs on a VM environment.
However, as Daniel says you could run into support problems with
Microsoft. I think the time problem only happens on ESX and I think it
is to do with the way ESX schedules the VMs or, to be more accurate,
doesn't if it doesn't need to because it seems the clocks always lose
time and never gain it.

 
Answer #4    Answered By: Joanne Greer     Answered On: Jan 21

I don't know the answer to your "how do I fix the time drift problem"
but if you are planning to go with Kerberos it becomes doubly important.

 
Answer #5    Answered By: Cathy Cameron     Answered On: Jan 21

I was not aware of this time drift problem associated with DCs and VMs.
I can understand the significance of this related to a domain  controller
and replication.

The reason I ask is that I thought I remembered way back in June 2006 at
TechEd that images were distributed of MOSS beta along with its own DC
to interact with. I wanted to replicate a similar environment. The
main reason being that we have a rigid process where I work, and a
WS2008 machine would immediately be flagged, so I wanted to work on this
in isolation through VM on my local machine. Perhaps there is an
alternate method for what I am attempting.

 
Answer #6    Answered By: Kerri Steele     Answered On: Jan 21

If you want to set this up for lab purposes only, then go right ahead. No
issues. If you are isolating it from your regular network and it will be
living in it's own world.

 
Answer #7    Answered By: Alisha Itagi     Answered On: Jan 21

Microsoft Office SharePoint Server 2007 VHD:
www.microsoft.com/.../details.aspx
db5-a47b-df17e14b2c74

 
Answer #8    Answered By: Octavio Dotson     Answered On: Jan 21

I have seen something similar to this. However after spending hrs on it ; it
turned out that this was related to the hardware. Do take a look at your server
infrastructure before spending too much time on this.

 
Didn't find what you were looking for? Find more on MOSS VMs, WS2008, AD Or get search suggestion and latest updates.




Tagged: