Bartosz Kowalski <BartoszKowalski@discussions.microsoft.com> wrote:
> Hello,
>
> When I login to PC as AD user, local profile (ie. folder tree in
> Documents and Settings) is created. Is it possible to do it by script?
>
> I need to do it for every user and computer in our AD

Can you please clarify what it is you're trying to do, and why?

Sometimes our PCs are working outside of AD with different users.
I want to make it possible for every user to work on a PC without AD
connection.
While logging on specific PC for the first time you need to have AD
connection, otherwise you receive a "user doesn't exist" message.

I want to make a script to "add" each AD users to PC.

I hope you understand what I need.

"Lanwench [MVP - Exchange]" wrote:

> Bartosz Kowalski <BartoszKowalski@discussions.microsoft.com> wrote:
> > Hello,
> >
> > When I login to PC as AD user, local profile (ie. folder tree in
> > Documents and Settings) is created. Is it possible to do it by script?
> >
> > I need to do it for every user and computer in our AD
>
> Can you please clarify what it is you're trying to do, and why?
>
>
>

Bartosz Kowalski wrote:

>Sometimes our PCs are working outside of AD with different users.
>I want to make it possible for every user to work on a PC without AD
>connection.
>While logging on specific PC for the first time you need to have AD
>connection, otherwise you receive a "user doesn't exist" message.
>
>I want to make a script to "add" each AD users to PC.
>
>I hope you understand what I need.

Creating a profile directory will not achieve this goal, as that doesn't
equate to having logged on at the PC.

There may be an API to create the logon profiles, but I suspect the
quickest way would simply be to logon to the PC using each AD account (if
you have access to the necessary passwords). RunAs offers the mechanism to
execute a command under different credentials and would be enough to cause
a profile to be instantiated.

Frankly, I'd say it's really not worth it. All you'll land up doing is
chewing up a lot of client PC disk space for no good reason. And, if you
enforce regular password changes (as you should), the profiles are going
to be inaccessible remotely anyway, since they'll have outdated password
hashes stored against them (ie the user would need to know their password
as it was at the time the profile was last accessed!).

It'd be easier to educate the users that if they want to use a machine
off-network, they must logon to it on-network first.

--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.