<div>
This sounds promising! &nbsp;I'm doing the upgrade this weekend, I'll give it a try once everything is set up and let you know if it worked.<br />
Thanks.
</div>


This sounds promising!  I'm doing the upgrade this weekend, I'll give it a try once everything is set up and let you know if it worked.
Thanks.

<div>
<div class="content wysiwyg-content">
I have just been given the task of implementing a simple Windows 2003 domain at work, but I have some concerns about maintaining the level and simplicity of remote users' access to network resources. &nbsp;Currently we have a basic Workgroup which all local computers are members of. &nbsp;Additionally, remote users (running Windows XP Pro on identically named workgroups) connect over a Sonicwall VPN to the work network, to access the fileserver etc. &nbsp;My concern is, once I implement the domain, how will this affect the remote users? &nbsp;I assume that they will have to be members of the domain in order to access it's resources? &nbsp;If so, how will this affect their access to the resources on their home workgroups? &nbsp;The situation I want to avoid is the remote users having to join the domain to access resources there, and then having to disjoin the domain to join the workgroup so that they can print and access other local resources.<br />
<br />
Can anyone help me out on this?
</div>
</div>


I have just been given the task of implementing a simple Windows 2003 domain at work, but I have some concerns about maintaining the level and simplicity of remote users' access to network resources.  Currently we have a basic Workgroup which all local computers are members of.  Additionally, remote users (running Windows XP Pro on identically named workgroups) connect over a Sonicwall VPN to the work network, to access the fileserver etc.  My concern is, once I implement the domain, how will this affect the remote users?  I assume that they will have to be members of the domain in order to access it's resources?  If so, how will this affect their access to the resources on their home workgroups?  The situation I want to avoid is the remote users having to join the domain to access resources there, and then having to disjoin the domain to join the workgroup so that they can print and access other local resources.

Can anyone help me out on this?

Accessing resources on a remote Windows 2003 Domain and a Home Workgroup

The Windows operating systems have distinct methodologies for designing and implementing networks, and have specific systems to accomplish various networking processes, such as Exchange for email, Sharepoint for shared files and programs, and IIS for delivery of web pages. Microsoft also produces server technologies for networked database use, security and virtualization.