|
The standalone server is in a workgroup. From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Parris Is the stand alone server a member of the
domain? I have had issues non vmware related where I could not promote a server
to become a DC if it was a member of the domain – I had to remove it
first then promote it – this was post sp1. From: Resend: I would like to add, Can anyone from Microsoft on this list
speak to what changed in Windows 2003 SP1 that would cause this symptom? Chuck From: Sorry to revive this one from the
archives, but it's been haunting me. I've experienced the same issue when
trying to promote a standalone W2K3 SP1 server to a domain controller. In an
attempt to further uncover the root cause of this nuisance I would like to add
the following. This problem seems to affect Windows
Server 2003 SP1 VM's running on VMware Workstation and ESX, even though ESX
doesn't use shared folders (haven't tested on GSX). If the VMware Tools Shared Folders
component is installed on a VM running on ESX (not default VMware Tools
installation on ESX hosted VM's) the issue still raises its ugly head. Also, a Windows Server 2003 (no SP1)
standalone server with the Shared Folders option installed does not experience
this symptom. So, the question is what changed in
Windows Server 2003 SP1 that is causing this symptom/problem? And is it Shared
Folders or something in Windows Server 2003 SP1 that is incompatible with
Shared Folders. Regards, Chuck From: Hi Everyone, As you all may know a few months ago I posted
two issues with Vmware and W2K3SP1 DCs. The issues described are:
Both the issues are described here:
This time a was setting up an environment with
a w2k forest and a w2k3 sp1 forest. When setting up the trust I received the
error we discussed a while ago (see articles above). A few days ago someone
posted which component caused this issue. The component in error seems to be
the "Shared Folder" component from Vmware (at least in Vmware Workstation).
This time instead of changing the password of the administrator account, I
deinstalled the "Shared Folder" component and rebooted the DC. After
that I was able to create the trust without any problem. So, the "Shared Folder" component
from Vmware does seem to be the root cause of this. Cheers, Met vriendelijke groet / Kind regards, Jorge de Almeida Pinto
LogicaCMG Nederland B.V. (BU
SD/AT) *
E-mail : [EMAIL PROTECTED] "
<http://www.logicacmg.com/> - Solutions that
matter - This e-mail and any attachment is for
authorised use by the intended recipient(s) only. It may contain proprietary
material, confidential information and/or be subject to legal privilege. It
should not be copied, disclosed to, retained or used by, any other party. If
you are not an intended recipient then please promptly delete this e-mail and
any attachment and all copies and inform the sender. Thank you. |
Title: FYI: W2K3 SP1 & VMWARE issue
