Question : Assign On Demand Vs. Assign Install At Login, On Demand vs Install at Login

You are the network administrator for ProzeWarez.net. Your network consists
of a single Active Directory domain named ProzeWarez.net. All servers run
Windows Server 2003. All user accounts in your domain are located in an
organizational unit (OU) named User Accounts.

User accounts are separated in two types: accounts for users who use portable
computers and accounts for users who use desktop computers. The accounts for
the users who use portable computers are in an OU named Portable, and the
accounts for the users who use desktop computers are in an OU named Desktop.

The OU structure is shown in the work area.

Users who use portable computers often travel with them, but they do not connect
to the network when they are out of the office.

You need to install an application on all client computers. Users must be able to run the
application even if the client computer is not connected to the network. You need to
perform the installation in a way that reduces network load on the installation source.

All software installed by using a Group Policy object (GPO) must require as little
support as possible. You need to configure Group Policy to install the application.
You also need to link any GPO to the appropriate OU.

What should you do? To answer, drag:


Three OUs and three possible actions:



............... O User Accounts
.. ............./ \
Portable O O Desktop



Possible Actions:

"Assign Install at Login"
"Publish"
"Assign Install on Demand"


My Answer: Assign at login to top OU - User accounts.

In this way- for the portables, the application will be loaded at next boot, or login.
The applicaiton will be loaded on portables, and can be used later, even of the
portable is not on the network. The application will be loaded on every client.


Or: Assign Portable - At login - Assign Desktops "On Demand" (The
On Demand does not 'assign to every client' (until it is need) - but this should
"reduce the network load".

Or: TK says: Top Level - Assign on Demand. Don't like this as it will
not be on the portable if the first demand is while the portable is on the road,
not on the network.


QUESTIONs: Does any of these options download the packet to the local computer,
then install it directly from a local drive? That would meet requirements best.

Do any of these options require that a network connection be maintained in order
for the application to continue to work?

Thanks for your thoughts on the subject...

Answer : Assign On Demand Vs. Assign Install At Login, On Demand vs Install at Login

Factors I would want to consider in my answer.....

number of remote users?
All users on same Timezone?
How many distribution points have you got?
All users work from single geographical office or from a WAN scenario?
Remote users have dialup or broadband access?
Size of download?
Do remote users need the app straightaway or can they wait till they get back in the office?
If there are issues, how am I going to support my remote users?

I'd do assign on demand for the remote OU (as you MAY have remote users already out on the road)
Assign on next login for pc users.

just my view