Know of a program to change Workgroup under NT?

[bigjon]

I need a program that will let me change the NT Workgroup and/or domain. Know of any (esp free ones)?

Thx

 

[skay]

Why can't you do it manually?

 

[SUOrangeman]

Right-click on Network Neighborhood (but you must be Admin).

-SUO

 

[bigjon]

LOL - actually, I'm writing a program (with Delphi) that will personalize an image after ghosting, and the workgroup is one of the user-specific bits of info. So, I need to programatically change the Workgroup. If nobody knows how to do this I could use SendKeys to simulate keystrokes into the Network Properties window.

This should probably be in the Programming forum, but the tricky part here is opening the Network Properties window through RUNDLL32, and that is more OS specific (anyone know the command)?

Sorry, should have clarified Thanks for the replies tho

Jon

 

[YoungFart]

<< LOL - actually, I'm writing a program (with Delphi) that will personalize an image after ghosting, and the workgroup is one of the user-specific bits of info. So, I need to programatically change the Workgroup. If nobody knows how to do this I could use SendKeys to simulate keystrokes into the Network Properties window.
>>



Correct me if I'm wrong, but
1. Computer name is &quot;user-specific&quot; too, so you'll have the same problem with it.
2. A computer account has to exist in the domain before it can join it. Do you plan to automate it too?

 

[bigjon]

AFAIK our company doesn't plan to ever use domains (we're running Novell). I'm really just interested in changing the workgroup (honestly I don't think it's necessary but it's a standard they had before we started using Ghost that we still have to follow). But yes, the username will always be assumed valid/existant.

I'm using GhostWalker to update the computer name/SID; it also happens to update the Host (on the DNS tab of TCP/IP properties). I've already automated creating a new local user account and updating the registry wherever the username appears; seems to be working fine.

Thanks for the comments - any more ideas/suggestions? We haven't actually started using Ghost in our company and I want to shoot down any potential problems before we go into production!