Re: Domain x Workspace

From: Chuck (none_at_example.net)
Date: 11/06/04 

Date: 6 Nov 2004 13:17:09 -0600

On Sat, 6 Nov 2004 16:06:18 -0300, "Luiz Horacio" <lhoracio@iname.com> wrote:

>Hi,
>
>I have a Windows XP Pro machine running inside a hospital. It has 2 users:
>one with administrative rights and another as a guest account.
>
>This week the IT people came and installed an application that will work
>with some kind of DB. And then the problem started. They said they needed to
>include my machine in a specific 'domain', but as it was installed my XP
>would only work in a 'workspace'.
>
>Now the weird part: they said I would need to reformat since the only way to
>do this 'domain' thing would be in the instalation process...
>
>Is this correct? I guess not, but would like to hear from you.
>
>What would they have to do to include my machine in this domain, and what
>needs to be done in the server side?
>
>
>Thanks,
>
>
>Luiz Horacio

Luiz,

In most cases, moving a computer from a workgroup environment to a domain
environment is a simple matter of joining the computer to the domain. This is
generally done by logging into the computer as an administrator, then joining
the domain as a domain administrator, from System Properties - Computer Name.

I, personally, know of no cases where reformatting (reinstalling the OS) is a
requirement to joining a computer to a domain.

I hate to second guess fellow techies, but, I'd bet your domain admins are
having you reformat, and reinstall the OS, as a security measure. They don't
have to worry about any hostile code (adware, spyware, viruses) that might have
been installed on your computer in the past.

This technique makes sense, at first glance. However:
1) If your computer was ever attached to their network, when a member of a
workgroup, it is still a threat WRT adware, spyware, and viruses. Not all
hostile code requires domain identity to spread thru a network.
2) Telling the user community (ie you) to reformat, and justifying that as a
prerequisite to joining the domain, is a bad relationship policy. IMHO.
3) Needless reformatting risks loss of data, and waste of time. Bad policy
from a management perspective.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

Relevant Pages

  • Re: How to get full access to all contents?
    ... The only user Name in "Users Who Can Transparently Access This File" in ... Agent Name" is Administrator. ... "ME" was my computer name before renaming. ... There was not a Local user with "ME" name before joining the domain. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Local Administrator
    ... > Is the PC actually a member of the domain, it would need to be to add the ... Logging in the domain and joining the computer to the domain are not the ... >> Administrator) but I don't have the domain available in the Locations ...
    (microsoft.public.windowsxp.general)
  • Re: Windows Log-In Password
    ... will be able to use the User Account app in control panel to ... To Logon as Default Administrator on Pro Edition, from Welcome screen, press ... > I've even tried to reformat again, ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: XP User Accounts
    ... Before you reformat and start over, ... your Administrator account is still named ... "Administrator" and the password is still "" - that is, Nil, or nothing. ... > Any way to get back to the way it was before I deleted the user accounts? ...
    (microsoft.public.windowsxp.general)
  • Re: I think I really screwed myself here...
    ... bathroom. ... administrator and taken admin priveledges away from my single user ... reformat at the time with the severe loss of drivers, ...
    (microsoft.public.windowsxp.help_and_support)