Guest AU Posted December 30, 2007 Posted December 30, 2007 Hello, All the foundation including the necessarily servers such as dc, file, dns, dhcp, print etc have been installed and given their appropriate information. (user accounts made, dhcp scope defined, GPs created, file quotas set). Basically everything fro the server side is completed; it's only the user side now. I now have the task to attach some 60+ users comprised of laptops and desktops to the domain. All of these users have been logging on to their local machine profile in a workgroup environment for the past 10+ years. Now my question is, how can I attach all of these users to the domain with the least amount of admin effort and interruptions on the user part. Thanks,
Guest Pegasus \(MVP\) Posted December 30, 2007 Posted December 30, 2007 Re: Best Approach to Attach Users to a new Domain "AU" <AU@discussions.microsoft.com> wrote in message news:11F4E852-ECEE-47F4-AC54-631E3CFC38DD@microsoft.com... > Hello, > > All the foundation including the necessarily servers such as dc, file, > dns, > dhcp, print etc have been installed and given their appropriate > information. > (user accounts made, dhcp scope defined, GPs created, file quotas set). > Basically everything fro the server side is completed; it's only the user > side now. > > I now have the task to attach some 60+ users comprised of laptops and > desktops to the domain. All of these users have been logging on to their > local machine profile in a workgroup environment for the past 10+ years. > > Now my question is, how can I attach all of these users to the domain with > the least amount of admin effort and interruptions on the user part. > > Thanks, This might help you: Automating the creation of computer accounts: http://support.microsoft.com/kb/315273 Make sure to test your script thoroughly.
Guest AU Posted December 30, 2007 Posted December 30, 2007 Re: Best Approach to Attach Users to a new Domain Hi, Wouldn't I still have to indivually go to each machine and log them on to the domain? When I join the domain won't it create the computer acct and then I'd simply move it to the correct OU in AD on the server side. I'm looking for solutions for the actual migration, such as if to migrate laptops or desktops first, etc etc. "Pegasus (MVP)" wrote: > > "AU" <AU@discussions.microsoft.com> wrote in message > news:11F4E852-ECEE-47F4-AC54-631E3CFC38DD@microsoft.com... > > Hello, > > > > All the foundation including the necessarily servers such as dc, file, > > dns, > > dhcp, print etc have been installed and given their appropriate > > information. > > (user accounts made, dhcp scope defined, GPs created, file quotas set). > > Basically everything fro the server side is completed; it's only the user > > side now. > > > > I now have the task to attach some 60+ users comprised of laptops and > > desktops to the domain. All of these users have been logging on to their > > local machine profile in a workgroup environment for the past 10+ years. > > > > Now my question is, how can I attach all of these users to the domain with > > the least amount of admin effort and interruptions on the user part. > > > > Thanks, > > This might help you: > Automating the creation of computer accounts: > http://support.microsoft.com/kb/315273 > Make sure to test your script thoroughly. > > >
Guest Pegasus \(MVP\) Posted December 30, 2007 Posted December 30, 2007 Re: Best Approach to Attach Users to a new Domain Have a look at the help built into netdom.exe. Among other things it says NETDOM JOIN machine /Domain:domain [/OU:ou path] [/userD:user] [/PasswordD:[password | *]] [userO:user] [/PasswordO:[password | *]] [/REBoot[:Time in seconds]] which implies that you can join a machine while sitting at your own console. Having played this game for many years, I would still go to each machine and perform a full logon process under the usual user's account name. Not doing so means that you will have a disaster at your hands on Monday morning. "AU" <AU@discussions.microsoft.com> wrote in message news:1B3CC631-C25C-47F5-B188-CDE8749BFFAD@microsoft.com... > Hi, > > Wouldn't I still have to indivually go to each machine and log them on to > the domain? When I join the domain won't it create the computer acct and > then I'd simply move it to the correct OU in AD on the server side. > > I'm looking for solutions for the actual migration, such as if to migrate > laptops or desktops first, etc etc. > > "Pegasus (MVP)" wrote: > >> >> "AU" <AU@discussions.microsoft.com> wrote in message >> news:11F4E852-ECEE-47F4-AC54-631E3CFC38DD@microsoft.com... >> > Hello, >> > >> > All the foundation including the necessarily servers such as dc, file, >> > dns, >> > dhcp, print etc have been installed and given their appropriate >> > information. >> > (user accounts made, dhcp scope defined, GPs created, file quotas set). >> > Basically everything fro the server side is completed; it's only the >> > user >> > side now. >> > >> > I now have the task to attach some 60+ users comprised of laptops and >> > desktops to the domain. All of these users have been logging on to >> > their >> > local machine profile in a workgroup environment for the past 10+ >> > years. >> > >> > Now my question is, how can I attach all of these users to the domain >> > with >> > the least amount of admin effort and interruptions on the user part. >> > >> > Thanks, >> >> This might help you: >> Automating the creation of computer accounts: >> http://support.microsoft.com/kb/315273 >> Make sure to test your script thoroughly. >> >> >>
Guest AU Posted January 2, 2008 Posted January 2, 2008 Re: Best Approach to Attach Users to a new Domain Sounds good, however you have made a good point. But in terms of the deployment process, should laptops be migrated first or desktops? "Pegasus (MVP)" wrote: > Have a look at the help built into netdom.exe. Among other things > it says > > NETDOM JOIN machine /Domain:domain [/OU:ou path] [/userD:user] > [/PasswordD:[password | *]] > [userO:user] [/PasswordO:[password | *]] > [/REBoot[:Time in seconds]] > > which implies that you can join a machine while sitting at your own > console. > > Having played this game for many years, I would still go to each > machine and perform a full logon process under the usual user's > account name. Not doing so means that you will have a disaster > at your hands on Monday morning. > > > "AU" <AU@discussions.microsoft.com> wrote in message > news:1B3CC631-C25C-47F5-B188-CDE8749BFFAD@microsoft.com... > > Hi, > > > > Wouldn't I still have to indivually go to each machine and log them on to > > the domain? When I join the domain won't it create the computer acct and > > then I'd simply move it to the correct OU in AD on the server side. > > > > I'm looking for solutions for the actual migration, such as if to migrate > > laptops or desktops first, etc etc. > > > > "Pegasus (MVP)" wrote: > > > >> > >> "AU" <AU@discussions.microsoft.com> wrote in message > >> news:11F4E852-ECEE-47F4-AC54-631E3CFC38DD@microsoft.com... > >> > Hello, > >> > > >> > All the foundation including the necessarily servers such as dc, file, > >> > dns, > >> > dhcp, print etc have been installed and given their appropriate > >> > information. > >> > (user accounts made, dhcp scope defined, GPs created, file quotas set). > >> > Basically everything fro the server side is completed; it's only the > >> > user > >> > side now. > >> > > >> > I now have the task to attach some 60+ users comprised of laptops and > >> > desktops to the domain. All of these users have been logging on to > >> > their > >> > local machine profile in a workgroup environment for the past 10+ > >> > years. > >> > > >> > Now my question is, how can I attach all of these users to the domain > >> > with > >> > the least amount of admin effort and interruptions on the user part. > >> > > >> > Thanks, > >> > >> This might help you: > >> Automating the creation of computer accounts: > >> http://support.microsoft.com/kb/315273 > >> Make sure to test your script thoroughly. > >> > >> > >> > > >
Guest Pegasus \(MVP\) Posted January 3, 2008 Posted January 3, 2008 Re: Best Approach to Attach Users to a new Domain Only you can answer this question. It depends on your users. "AU" <AU@discussions.microsoft.com> wrote in message news:3901EC48-E5C7-47F7-8716-3B8E6A3B087C@microsoft.com... > Sounds good, however you have made a good point. > But in terms of the deployment process, should laptops be migrated first > or > desktops? > > "Pegasus (MVP)" wrote: > >> Have a look at the help built into netdom.exe. Among other things >> it says >> >> NETDOM JOIN machine /Domain:domain [/OU:ou path] [/userD:user] >> [/PasswordD:[password | *]] >> [userO:user] [/PasswordO:[password | *]] >> [/REBoot[:Time in seconds]] >> >> which implies that you can join a machine while sitting at your own >> console. >> >> Having played this game for many years, I would still go to each >> machine and perform a full logon process under the usual user's >> account name. Not doing so means that you will have a disaster >> at your hands on Monday morning. >> >> >> "AU" <AU@discussions.microsoft.com> wrote in message >> news:1B3CC631-C25C-47F5-B188-CDE8749BFFAD@microsoft.com... >> > Hi, >> > >> > Wouldn't I still have to indivually go to each machine and log them on >> > to >> > the domain? When I join the domain won't it create the computer acct >> > and >> > then I'd simply move it to the correct OU in AD on the server side. >> > >> > I'm looking for solutions for the actual migration, such as if to >> > migrate >> > laptops or desktops first, etc etc. >> > >> > "Pegasus (MVP)" wrote: >> > >> >> >> >> "AU" <AU@discussions.microsoft.com> wrote in message >> >> news:11F4E852-ECEE-47F4-AC54-631E3CFC38DD@microsoft.com... >> >> > Hello, >> >> > >> >> > All the foundation including the necessarily servers such as dc, >> >> > file, >> >> > dns, >> >> > dhcp, print etc have been installed and given their appropriate >> >> > information. >> >> > (user accounts made, dhcp scope defined, GPs created, file quotas >> >> > set). >> >> > Basically everything fro the server side is completed; it's only the >> >> > user >> >> > side now. >> >> > >> >> > I now have the task to attach some 60+ users comprised of laptops >> >> > and >> >> > desktops to the domain. All of these users have been logging on to >> >> > their >> >> > local machine profile in a workgroup environment for the past 10+ >> >> > years. >> >> > >> >> > Now my question is, how can I attach all of these users to the >> >> > domain >> >> > with >> >> > the least amount of admin effort and interruptions on the user part. >> >> > >> >> > Thanks, >> >> >> >> This might help you: >> >> Automating the creation of computer accounts: >> >> http://support.microsoft.com/kb/315273 >> >> Make sure to test your script thoroughly. >> >> >> >> >> >> >> >> >>
Recommended Posts