[gptalk] Re: Determining if Group Policy Deployment is right for us....
- From: "Steve Rochford" <Steve.Rochford@xxxxxxxxxx>
- To: <gptalk@xxxxxxxxxxxxx>
- Date: Wed, 5 Mar 2008 16:34:54 -0000
Not sure if a behaviour I've seen is general with patching like this or
was just an "issue" with Microsoft Office.
When we first deployed Office 2000 we used an admin install. At some
point a service pack came out so we patched the installation point. We
didn't re-deploy immediately, just let this install to new machines.
This causes problems. If you have software (like Office) which can have
some features set to "install on first use" they go back to this install
point and find it's not what they expect and fall-over. You can, of
course, force a redeployment but this is time consuming and not always
easy to get done.
Since then, we've always made a second deployment if there's a patch -
eg folder called "office" and then "office_sp1" etc. New machines get
pointed to the office_sp1 folder, old machines can continue to work with
the old folder.
Steve
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
On Behalf Of Matt Walker
Sent: 05 March 2008 14:59
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: Determining if Group Policy Deployment is right
for us....
I found this from http://support.microsoft.com/kb/226936 :
"This command replaces the necessary files on the network share and
updates the .msi file for proper installation using the new components."
I'm guessing this answers my latest question(s).
Sorry for being such a pain in the backside about this, but I do
appreciate all of the Help!
Matt Walker
Installation Development
Synergis Software
472 California Road | Quakertown, PA 18951
Phone: 215.529.9900, x192 | 800.836.5440
Fax: 215.536.9249
www.synergis-adept.com <http://www.synergis-adept.com/>
Simple, Powerful Document Management
This message (and any associated files) is intended only for the use of
the individual or entity to which it is addressed and may contain
information that is confidential, subject to copyright or constitutes a
trade secret. If you are not the intended recipient you are hereby
notified that any dissemination, copying or distribution of this
message, or files associated with this message, is strictly prohibited.
If you have received this message in error, please notify us immediately
by replying to the message and deleting it from your computer. Messages
sent to and from us may be monitored.
Internet communications cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. Therefore, we do not accept
responsibility for any errors or omissions that are present in this
message, or any attachment, that have arisen as a result of e-mail
transmission. If verification is required, please request a hard-copy
version. Any views or opinions presented are solely those of the author
and do not necessarily represent those of the company.
________________________________
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
On Behalf Of Darren Mar-Elia
Sent: Wednesday, March 05, 2008 9:35 AM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: Determining if Group Policy Deployment is right
for us....
What the approach is, and I think I mention this in the whitepaper, is
that you patch the distribution point using msiexec, then issue a
re-deploy on the package in GPO. This tells the clients to essentially
"repair" the package, and they thus pick up the new bits.
Darren
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
On Behalf Of Matt Walker
Sent: Wednesday, March 05, 2008 8:20 AM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: Determining if Group Policy Deployment is right
for us....
How do you mean apply the patch with msiexec? Is the patched pushed
through Group policy and kicked off or is there something that has to be
done at each workstation?
Matt Walker
Installation Development
Synergis Software
472 California Road | Quakertown, PA 18951
Phone: 215.529.9900, x192 | 800.836.5440
Fax: 215.536.9249
www.synergis-adept.com <http://www.synergis-adept.com/>
Simple, Powerful Document Management
This message (and any associated files) is intended only for the use of
the individual or entity to which it is addressed and may contain
information that is confidential, subject to copyright or constitutes a
trade secret. If you are not the intended recipient you are hereby
notified that any dissemination, copying or distribution of this
message, or files associated with this message, is strictly prohibited.
If you have received this message in error, please notify us immediately
by replying to the message and deleting it from your computer. Messages
sent to and from us may be monitored.
Internet communications cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. Therefore, we do not accept
responsibility for any errors or omissions that are present in this
message, or any attachment, that have arisen as a result of e-mail
transmission. If verification is required, please request a hard-copy
version. Any views or opinions presented are solely those of the author
and do not necessarily represent those of the company.
________________________________
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
On Behalf Of Darren Mar-Elia
Sent: Wednesday, March 05, 2008 9:18 AM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: Determining if Group Policy Deployment is right
for us....
Yes. You have to use msiexec to apply the patch to your distribution
point, but it will work that way.
Darren
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
On Behalf Of Matt Walker
Sent: Wednesday, March 05, 2008 7:34 AM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: Determining if Group Policy Deployment is right
for us....
Ah, so if I deploy an .msi then need to patch, Group Policy can handle
just using the .msp file and get that to the Clients?
Matt Walker
Installation Development
Synergis Software
472 California Road | Quakertown, PA 18951
Phone: 215.529.9900, x192 | 800.836.5440
Fax: 215.536.9249
www.synergis-adept.com <http://www.synergis-adept.com/>
Simple, Powerful Document Management
This message (and any associated files) is intended only for the use of
the individual or entity to which it is addressed and may contain
information that is confidential, subject to copyright or constitutes a
trade secret. If you are not the intended recipient you are hereby
notified that any dissemination, copying or distribution of this
message, or files associated with this message, is strictly prohibited.
If you have received this message in error, please notify us immediately
by replying to the message and deleting it from your computer. Messages
sent to and from us may be monitored.
Internet communications cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. Therefore, we do not accept
responsibility for any errors or omissions that are present in this
message, or any attachment, that have arisen as a result of e-mail
transmission. If verification is required, please request a hard-copy
version. Any views or opinions presented are solely those of the author
and do not necessarily represent those of the company.
________________________________
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
On Behalf Of Darren Mar-Elia
Sent: Tuesday, March 04, 2008 7:19 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: Determining if Group Policy Deployment is right
for us....
Matt-
I will answer the automated updating question first. You could schedule
this using this, for example, a script that ran through Task Scheduler
that issued a reboot across your workstations, since that would trigger
the install.
In terms of admin installs and patching, the examples in the whitepaper
are based on products like Office, which support the notion of an
administrative install and also support .MSP patching. .MSP files
generally need to be applied to an administrative install, rather than a
regular install, to be picked up correctly by the clients. However, your
own package probably does not need to worry about this, assuming you
patch your files using .MSP.
Darren
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
On Behalf Of Matt Walker
Sent: Tuesday, March 04, 2008 2:01 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: Determining if Group Policy Deployment is right
for us....
I see in the whitepaper a mention of Windows Installer administrative
install (/a). Is this always necessary? Is it something that is done
through normal GPO deployment or is this a manual step?
In the whitepaper, it is mentioned in the contact of patching a
previously deployed package, which may occur in our scenario. In
following the paper, I point to the .msi for the initial deployment with
no mention of the admin. install at that time. I'm just not sure how to
do the patching if the /a option was not used for initial deployment.
I'm just a little confused with this part (so far).
________________________________
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
On Behalf Of Nelson, Jamie R
Sent: Tuesday, March 04, 2008 2:47 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: Determining if Group Policy Deployment is right
for us....
Updating will always require some kind of administrator involvement
regardless of what deployment method you use (unless of course you
actually design an auto-update feature that is specific to your
application). Scheduling, as previous mentioned, is not possible because
your computer assigned software installation policy will always be
dependent on a reboot of the machine.
Jamie Nelson | Systems Engineer | Systems Support, Information
Technology | I N T E G R I S Health | Phone 405.552.0903 | Fax
405.553.5687 | http://www.integrisok.com <http://www.integrisok.com/>
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
On Behalf Of Matt Walker
Sent: Tuesday, March 04, 2008 1:27 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: Determining if Group Policy Deployment is right
for us....
Also, what are the limitations of Group Policy with regard to
scheduling, auto updating, and reporting? I've read that these cannot
be done or are of limited functionality. For updating, how automated
can it be? Does there always have to be Administrator involvement?
Any further information appreciated!
Thanks much!!
Matt Walker
Installation Development
Synergis Software
472 California Road | Quakertown, PA 18951
Phone: 215.529.9900, x192 | 800.836.5440
Fax: 215.536.9249
www.synergis-adept.com <http://www.synergis-adept.com/>
Simple, Powerful Document Management
This message (and any associated files) is intended only for the use of
the individual or entity to which it is addressed and may contain
information that is confidential, subject to copyright or constitutes a
trade secret. If you are not the intended recipient you are hereby
notified that any dissemination, copying or distribution of this
message, or files associated with this message, is strictly prohibited.
If you have received this message in error, please notify us immediately
by replying to the message and deleting it from your computer. Messages
sent to and from us may be monitored.
Internet communications cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. Therefore, we do not accept
responsibility for any errors or omissions that are present in this
message, or any attachment, that have arisen as a result of e-mail
transmission. If verification is required, please request a hard-copy
version. Any views or opinions presented are solely those of the author
and do not necessarily represent those of the company.
________________________________
This e-mail may contain identifiable health information that is subject
to protection under state and federal law. This information is intended
to be for the use of the individual named above. If you are not the
intended recipient, be aware that any disclosure, copying, distribution
or use of the contents of this information is prohibited and may be
punishable by law. If you have received this electronic transmission in
error, please notify us immediately by electronic mail (reply).
________________________________
This e-mail may contain identifiable health information that is subject
to protection under state and federal law. This information is intended
to be for the use of the individual named above. If you are not the
intended recipient, be aware that any disclosure, copying, distribution
or use of the contents of this information is prohibited and may be
punishable by law. If you have received this electronic transmission in
error, please notify us immediately by electronic mail (reply).
Other related posts:
