| Author | Messages | |
DaemonRoot
Posts:26
 | | 08/20/2010 4:20 PM |
| So I found this document that is very good and detailed about software
assignment and management thru GPOs.
http://technet.microsoft.com/en-us/library/bb742421.aspx
Problem is that it reads "Windows 2000" so my customer is not happy with it
since their environment is Windows 2003.
The part I am interested is this:
Publish to Users
Assign to Users
Assign to Computers
After the administrator deploys the software, it is available for
installation:
If an application is deployed in a GPO that is already applied to the user
from a previous logon, it is available for installation in the current logon
session (from the Add/Remove Programs Control Panel). If the application is
deployed in a new GPO that is not already associated with the user, then it
is available at the next logon.
If an application is deployed in a GPO that is already applied to the user
from a previous logon, it is available for installation in the current logon
session (from the Add/Remove Programs Control Panel). If the application is
deployed in a new GPO that is not already associated with the user, then it
is available at the next logon.
The next time the computer starts (reboot).
I tested assigning a package to a computer's group and yes, it was available
after a reboot just as the document states.
Any document out there that covers Windows 2003 or 2008?
~D
| | | |
| dmarelia
Posts:394
| | 08/20/2010 4:49 PM |
| Daniel-
I'm not sure I've seen anything specific to GPSI. Frankly, not much has changed in GPSI since Windows 2000. The only change that I'm aware of is that they added the ability to trigger an install at logon time for a user-assigned package. In Win2k, you could only "advertise" to a user, which meant the package was installed on first use. In Win2K3, they added the ability to force the installation at user logon regardless of any user action. Seriously that is about the only thing of substance that has changed since Win2k.
Darren
From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Castillo, Daniel (Directory Services)
Sent: Friday, August 20, 2010 7:53 AM
To: xxxxxxxxxxxxxxxx
Subject: [gptalk] Updated version.
So I found this document that is very good and detailed about software assignment and management thru GPOs.
http://technet.microsoft.com/en-us/library/bb742421.aspx
Problem is that it reads "Windows 2000" so my customer is not happy with it since their environment is Windows 2003.
The part I am interested is this:
Publish to Users
Assign to Users
Assign to Computers
After the administrator deploys the software, it is available for installation:
If an application is deployed in a GPO that is already applied to the user from a previous logon, it is available for installation in the current logon session (from the Add/Remove Programs Control Panel). If the application is deployed in a new GPO that is not already associated with the user, then it is available at the next logon.
If an application is deployed in a GPO that is already applied to the user from a previous logon, it is available for installation in the current logon session (from the Add/Remove Programs Control Panel). If the application is deployed in a new GPO that is not already associated with the user, then it is available at the next logon.
The next time the computer starts (reboot).
I tested assigning a package to a computer's group and yes, it was available after a reboot just as the document states.
Any document out there that covers Windows 2003 or 2008?
~D
| | | |
| thorbjornsjovold
Posts:16
| | 08/23/2010 3:06 PM |
| As Darren states, it works the same for all versions of Windows with very little changes, but there is a catch in XP and forward. So on top of what Darren already stated, there is a minor tweak to make it possible to prevent x86 windows installer packages from installing on x64 boxes that did not exist on W2K. And also more importantly; GP processing was changed in XP so depending on if you have disabled Fast Logon Optimization, http://technet.microsoft.com/en-us/library/cc758898(WS.10).aspx or not, it can take more than one reboot/logon to get the software on XP/Vista/7 boxes by default.
HTH,
Thorbjörn Sjövold
Specops Software
xxxxxxxxxxxxxxxx | www.specopssoft.com<http://www.specopssoft.com/>
From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia
Sent: den 20 augusti 2010 17:23
To: xxxxxxxxxxxxxxxx
Subject: RE: [gptalk] Updated version.
Daniel-
I'm not sure I've seen anything specific to GPSI. Frankly, not much has changed in GPSI since Windows 2000. The only change that I'm aware of is that they added the ability to trigger an install at logon time for a user-assigned package. In Win2k, you could only "advertise" to a user, which meant the package was installed on first use. In Win2K3, they added the ability to force the installation at user logon regardless of any user action. Seriously that is about the only thing of substance that has changed since Win2k.
Darren
From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Castillo, Daniel (Directory Services)
Sent: Friday, August 20, 2010 7:53 AM
To: xxxxxxxxxxxxxxxx
Subject: [gptalk] Updated version.
So I found this document that is very good and detailed about software assignment and management thru GPOs.
http://technet.microsoft.com/en-us/library/bb742421.aspx
Problem is that it reads "Windows 2000" so my customer is not happy with it since their environment is Windows 2003.
The part I am interested is this:
Publish to Users
Assign to Users
Assign to Computers
After the administrator deploys the software, it is available for installation:
If an application is deployed in a GPO that is already applied to the user from a previous logon, it is available for installation in the current logon session (from the Add/Remove Programs Control Panel). If the application is deployed in a new GPO that is not already associated with the user, then it is available at the next logon.
If an application is deployed in a GPO that is already applied to the user from a previous logon, it is available for installation in the current logon session (from the Add/Remove Programs Control Panel). If the application is deployed in a new GPO that is not already associated with the user, then it is available at the next logon.
The next time the computer starts (reboot).
I tested assigning a package to a computer's group and yes, it was available after a reboot just as the document states.
Any document out there that covers Windows 2003 or 2008?
~D
| | | |
| DaemonRoot
Posts:26
| | 08/23/2010 8:59 PM |
| Great, this is what I was looking for.
Thank you guys.
~D
From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx]
On Behalf Of Thorbjörn Sjövold
Sent: Monday, August 23, 2010 7:32 AM
To: xxxxxxxxxxxxxxxx
Subject: RE: [gptalk] Updated version.
As Darren states, it works the same for all versions of Windows with very
little changes, but there is a catch in XP and forward. So on top of what
Darren already stated, there is a minor tweak to make it possible to prevent
x86 windows installer packages from installing on x64 boxes that did not
exist on W2K. And also more importantly; GP processing was changed in XP so
depending on if you have disabled Fast Logon Optimization,
http://technet.microsoft.com/en-us/library/cc758898(WS.10).aspx or not, it
can take more than one reboot/logon to get the software on XP/Vista/7 boxes
by default.
HTH,
Thorbjörn Sjövold
Specops Software
xxxxxxxxxxxxxxxx | <http://www.specopssoft.com/>
www.specopssoft.com
From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx]
On Behalf Of Darren Mar-Elia
Sent: den 20 augusti 2010 17:23
To: xxxxxxxxxxxxxxxx
Subject: RE: [gptalk] Updated version.
Daniel-
Im not sure Ive seen anything specific to GPSI. Frankly, not much has
changed in GPSI since Windows 2000. The only change that Im aware of is
that they added the ability to trigger an install at logon time for a
user-assigned package. In Win2k, you could only advertise to a user, which
meant the package was installed on first use. In Win2K3, they added the
ability to force the installation at user logon regardless of any user
action. Seriously that is about the only thing of substance that has changed
since Win2k.
Darren
From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx]
On Behalf Of Castillo, Daniel (Directory Services)
Sent: Friday, August 20, 2010 7:53 AM
To: xxxxxxxxxxxxxxxx
Subject: [gptalk] Updated version.
So I found this document that is very good and detailed about software
assignment and management thru GPOs.
http://technet.microsoft.com/en-us/library/bb742421.aspx
Problem is that it reads Windows 2000 so my customer is not happy with it
since their environment is Windows 2003.
The part I am interested is this:
Publish to Users
Assign to Users
Assign to Computers
After the administrator deploys the software, it is available for
installation:
If an application is deployed in a GPO that is already applied to the user
from a previous logon, it is available for installation in the current logon
session (from the Add/Remove Programs Control Panel). If the application is
deployed in a new GPO that is not already associated with the user, then it
is available at the next logon.
If an application is deployed in a GPO that is already applied to the user
from a previous logon, it is available for installation in the current logon
session (from the Add/Remove Programs Control Panel). If the application is
deployed in a new GPO that is not already associated with the user, then it
is available at the next logon.
The next time the computer starts (reboot).
I tested assigning a package to a computers group and yes, it was available
after a reboot just as the document states.
Any document out there that covers Windows 2003 or 2008?
~D
| | | |
|
|