| Author | Messages | |
Shanzao
Posts:45
 | | 09/24/2010 2:47 PM |
| I really think I need some looking at this script also, currently in my environment, I use GPOs to do all this work, but I think I may have missed something... All my servers only restart when needed, they only apply the GPOs when needed, but I feel left out and would also like this script ;o)
-----Original Message-----
From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darragh O'Shaughnessy
Sent: 24 September 2010 14:08
To: xxxxxxxxxxxxxxxx
Subject: RE: [gptalk] Restarting servers and automatic updating
Yes I had looked at that option in light of this thread but I wanted my
admins to do the updates themselves (especially on database servers etc.). I
have a very simple script that simple notifies and mailbox that a server
requires a reboot.
I implemented it in Vbscript as I wanted it to run natively without and
framework requirements.
I'll post it when I find it. It was only a couple of lines of code
-----Original Message-----
From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx]
On Behalf Of Joe Pochedley
Sent: 24 September 2010 14:00
To: xxxxxxxxxxxxxxxx
Subject: RE: [gptalk] Restarting servers and automatic updating
Darragh,
I've looked at Kevin's script (thanks again, Kevin). It does a nice job of
downloading and applying updates through the Microsoft.Update.Session
object... (Probably exactly what you tried to avoid. ) It also
writes very nice status messages in the event log for success or failure of
the various steps in the process.
If I had one complaint, it's that the script will reboot a machine whether
or not any update truly requires a restart... Of course, 95% of the time,
some update in the pile does require a restart, so it's probably not that
big a deal... But even then there's still 'some' unnecessary rebooting
going on.... Maybe we can combine your registry check with Kevin's script
to only reboot the when it's truly required. That would be ideal.
Look forward to seeing your code!
Joe Pochedley
-----Original Message-----
From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx]
On Behalf Of Darragh O'Shaughnessy
Sent: Friday, September 24, 2010 8:21 AM
To: xxxxxxxxxxxxxxxx
Subject: RE: [gptalk] Restarting servers and automatic updating
Kevin,
I have a vb script that does this (i.e. detects if the server requires
updates) and reboots the server. It does this by checking a registry key. It
only detects updates installed by WU that require a reboot, not manually
installed updates (i.e. updates run outside of the Windows Update Agent
GUI).
I will dig it up and post here as it seems to be much wanted. I'd be
interested in seeing how you accomplished it also? I tried initially using
the API but it didn't appear to expose this readily without creating an
Installation object which is overkill.
Darragh O'Shaughnessy
-----Original Message-----
From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx]
On Behalf Of Shane Williford
Sent: 24 September 2010 13:14
To: xxxxxxxxxxxxxxxx
Subject: RE: [gptalk] Restarting servers and automatic updating
Me three...or ten, whichever number I am!
Shane M. Williford
Systems Administrator
VCP3, MCSE, MCSA Sec, Sec+, Net+, A+
Mazuma Credit Union
Kansas City, MO 64131
xxxxxxxxxxxxxxxx
(816) 361-4194 x6012
-----Original Message-----
From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx]
On Behalf Of Robert K Coffman Jr. -Info From Data Corp.
Sent: Friday, September 24, 2010 7:10 AM
To: xxxxxxxxxxxxxxxx
Subject: Re: [gptalk] Restarting servers and automatic updating
Me too!
- Bob Coffman
On 9/24/2010 2:50 AM, Peter Gough wrote:
> Hi,
>
> I'd like to add another vote to the 'me too' comments. Any chance of
> posting the code?
>
> Many thanks,
>
> Peter
>
> On 22 September 2010 03:08, Doug Neely <xxxxxxxxxxxxxxxx
> <mailto:xxxxxxxxxxxxxxxx>> wrote:
>
> Me too!
>
> *From:* xxxxxxxxxxxxxxxx
> <mailto:xxxxxxxxxxxxxxxx>
> [mailto:xxxxxxxxxxxxxxxx
> <mailto:xxxxxxxxxxxxxxxx>] *On Behalf Of *Derek Rose
> *Sent:* Tuesday, September 21, 2010 10:39 AM
>
>
> *To:* xxxxxxxxxxxxxxxx <mailto:xxxxxxxxxxxxxxxx>
> *Subject:* RE: [gptalk] Restarting servers and automatic updating
>
> Me too
>
> *From:* xxxxxxxxxxxxxxxx
> <mailto:xxxxxxxxxxxxxxxx>
> [mailto:xxxxxxxxxxxxxxxx
> <mailto:xxxxxxxxxxxxxxxx>] *On Behalf Of *Scott Klassen
> *Sent:* Tuesday, September 21, 2010 11:20 AM
> *To:* xxxxxxxxxxxxxxxx <mailto:xxxxxxxxxxxxxxxx>
> *Subject:* RE: [gptalk] Restarting servers and automatic updating
>
> Jumping on the Kevin bandwagon. One more here interested.
>
> Scott Klassen
>
> *From:* xxxxxxxxxxxxxxxx
> <mailto:xxxxxxxxxxxxxxxx>
> [mailto:xxxxxxxxxxxxxxxx
> <mailto:xxxxxxxxxxxxxxxx>] *On Behalf Of *Darragh
> O'Shaughnessy
> *Sent:* Tuesday, September 21, 2010 8:32 AM
> *To:* xxxxxxxxxxxxxxxx <mailto:xxxxxxxxxxxxxxxx>
> *Subject:* RE: [gptalk] Restarting servers and automatic updating
>
> Kevin, I'd like a look at your script too. I wouldn't mind adding
> some simple alert mailing capability to it for our dev teams who
> look after rebooting dev servers when they are patched. You'd save
> me some work! J
>
> Darragh O'Shaughnessy
>
> *From:* xxxxxxxxxxxxxxxx
> <mailto:xxxxxxxxxxxxxxxx>
> [mailto:xxxxxxxxxxxxxxxx
> <mailto:xxxxxxxxxxxxxxxx>] *On Behalf Of *Craig Meyer
> (Hotmail)
> *Sent:* 21 September 2010 14:18
> *To:* xxxxxxxxxxxxxxxx <mailto:xxxxxxxxxxxxxxxx>
> *Subject:* Re: [gptalk] Restarting servers and automatic updating
>
> Just want to say thank you to Kevin for providing me with this script
>
> A very nice piece of work that will be saving me lots of time in
> future.
>
> Thanks Kevin
>
> *From:* Wornell, Kevin (Dallas)
<mailto:xxxxxxxxxxxxxxxx>
>
> *Sent:* Monday, September 20, 2010 3:22 PM
>
> *To:* xxxxxxxxxxxxxxxx <mailto:xxxxxxxxxxxxxxxx>
>
> *Subject:* RE: [gptalk] Restarting servers and automatic updating
>
> I wrote a small VB app that does this in our environment. This app
> basically checks to see if updates are needed based on the WSUS
> server of record, then applies them if needed, and then reboots the
> machine if required. If updates have been previously applied and a
> reboot is needed then it simply reboots the computer. We run this
> as a scheduled task during the maintenance window using GPP files to
> get the exe local and then the task can run it.
>
> I could take a look at stripping out the bits that are specific to
> our environment if you think this would help you.
>
> *Kevin*
>
> * *
>
> *Kevin Wornell**
> *Sr. Technical Engineer
> Towers Watson
> Suite 4100, 500 N. Akard Street | Dallas, TX, 75201
> Phone: 214.530.4057 | Fax: 214.988.5711
> xxxxxxxxxxxxxxxx <mailto:xxxxxxxxxxxxxxxx>
> www.towerswatson.com <http://www.towerswatson.com>
>
> *From:* xxxxxxxxxxxxxxxx
> <mailto:xxxxxxxxxxxxxxxx>
> [mailto:xxxxxxxxxxxxxxxx
> <mailto:xxxxxxxxxxxxxxxx>] *On Behalf Of *Craig Meyer
> (Hotmail)
> *Sent:* Monday, September 20, 2010 4:39 AM
> *To:* xxxxxxxxxxxxxxxx <mailto:xxxxxxxxxxxxxxxx>
> *Subject:* [gptalk] Restarting servers and automatic updating
>
> Hi all
>
> Is it possible to implement a GPO to do the following?
>
> To monitor a group of servers and during a maintenance window (eg
> Sunday morning 1am to 5am) reboot all the Windows Servers that got
> windows updates in the week and require a reboot. In other words all
> those servers with those annoying pop-ups saying updates have been
> installed and they require a reboot?
>
> thanks in advance
>
> /Notice of Confidentiality/
>
> This transmission contains information that may be confidential. It
> has been prepared for the sole and exclusive use of the intended
> recipient and on the basis agreed with that person. If you are not
> the intended recipient of the message (or authorized to receive it
> for the intended recipient), you should notify us immediately; you
> should delete it from your system and may not disclose its contents
> to anyone else.
>
> This e-mail has come to you from Towers Watson Delaware Inc.
>
> CONFIDENTIALITY NOTICE: This e-mail message (including attachments)
> is covered by the Electronic Communications Privacy Act, 18 U.S.C.
> 2510-2521, and is intended only for the person or entity to which it
> is addressed and may contain confidential and/or privileged
> material. Any unauthorized review, use, disclosure, dissemination,
> copying, forwarding or distribution is prohibited. If you are not
> the intended recipient, please contact the sender by reply e-mail
> and destroy all copies of the original message. If you are the
> intended recipient but do not wish to receive communication through
> this medium, please so advise the sender immediately.
>
>
Notice: The information transmitted in this e-mail may contain confidential
and/ or legally privileged information intended only for the use of the
individual(s) named above. Review, use, disclosure, distribution, or
forwarding of this information by persons or entities other than the
intended recipient(s) is prohibited by law and may subject them to criminal
or civil liabilities. Statements and opinion expressed in this e-mail may
not represent those of Mazuma Credit Union. All e-mail communications
through Mazuma's corporate email system are subject to archiving and review
by someone other than the recipient. If you have received this communication
in error, please notify the sender immediately and delete/destroy any and
all copies of the original message from any computer or network system.
This email originates from AXA Technology Services UK Limited (reg.
no. 1854856) which has its registered office at 5 Old Broad Street,
London EC2N 1AD, England.
This message and any files transmitted with it are confidential and
intended solely for the individual or entity to whom they are addressed.
If you have received this in error, you should not disseminate or copy
this email. Please notify the sender immediately and delete this email
from your system.
Please also note that any opinions presented in this email are solely
those of the author and do not necessarily represent those of The AXA
UK Plc Group.
Email transmission cannot be guaranteed to be secure, or error free as
information could be intercepted, corrupted, lost, destroyed, late in
arriving or incomplete as a result of the transmission process. The
sender therefore does not accept liability for any errors or omissions in
the contents of this message which arise as a result of email
transmission.
Finally, the recipient should check this email and any attachments for
viruses. The AXA UK Plc Group accept no liability for any damage
caused by any virus transmitted by this email.
| | | |
| DarraghOShaughnessy
Posts:177
| | 09/24/2010 3:22 PM |
| Ok, here is guts of a very simple script I used with SCOM and a GPP
scheduled task (depending on whether the server had an SCOM agent on it).
I've amended it to show different ways of detecting the reboot requirement.
I also had it read from an .xml file and email the owners of the servers
letting them know they must reboot. It's easily adaptable to reboot the
server or whatever you need.
My goal was simple:
* For servers that have yet to have the updates installed, notify
the admins that they need to do so via email (an additional part of the
script which I haven't included and in fact runs on the WSUS server)
* For servers that have had the updates installed, notify the admins
to reboot as this should be done ASAP after updates are installed.
Hopefully this helps some of you guys out. Let me know of any bugs. It
doesn't make any changes to your systems.
Systems tested on:
A. Windows XP SP3
B. Windows 2003 x86
C. Windows 2008 x86/x64
Darragh O'Shaughnessy
_____
'@Author Darragh O'Shaughnessy
Option explicit
On error resume next
loginfo "Script started"
const HKEY_LOCAL_MACHINE = "HKLM"
Const RET_REBOOT_REQUIRED=1000
Const RET_REBOOT_NOT_REQUIRED=1001
Const strKeyPath =
"SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto
Update\RebootRequired\"
Const REGREAD_NOT_EXIST = -2147024894
Const REGREAD_EXIST = 0
Const RET_REBOOT_UNKNOWN = -1
Dim strComputer,objRegistry
'Get agent version
Dim oAgentInfo: Set oAgentInfo = CreateObject("Microsoft.Update.AgentInfo")
If Err.Number <> 0 Then logErr "Could not create
object:Microsoft.Update.AgentInfo",False,true
loginfo "Object created:Microsoft.Update.AgentInfo"
loginfo "C:\Windows\System32\wuapi.dll version: " &
oAgentInfo.GetInfo("ProductVersionString")
loginfo "WUA version : " & oAgentInfo.GetInfo("ApiMajorVersion") & "." &
oAgentInfo.GetInfo("ApiMinorVersion")
'Ask agent for version and reboot status
Set oAgentInfo = CreateObject("Microsoft.Update.SystemInfo")
If Err.Number <> 0 Then logErr "Could not create
object:Microsoft.Update.SystemInfo",False,true
loginfo "Object created:Microsoft.Microsoft.Update.SystemInfo"
loginfo "Agent Reboot required: " & oAgentInfo.RebootRequired
'Check registry for same
Dim WshShell,intRet
Set WshShell = WScript.CreateObject("Wscript.Shell")
intRet = RegistryKeyExists(WshShell,HKEY_LOCAL_MACHINE,strKeyPath)
If(intRet = REGREAD_EXIST) Then
loginfo "Registry Reboot Status: Required"
WScript.Quit RET_REBOOT_REQUIRED
ElseIf(intRet = REGREAD_NOT_EXIST) Then
loginfo "Registry Reboot Status: NOt Required"
WScript.Quit RET_REBOOT_REQUIRED
Else
loginfo "Registry Reboot Status: Undetermimed!"
WScript.Quit RET_REBOOT_UNKNOWN
End If
WScript.Quit
Function RegistryKeyExists(byref WshShell, hkroot, strKey)
'See: http://msdn.microsoft.com/en-us/library/x05fawxd%28VS.85%29.aspx
On Error Resume next
loginfo "Checking registry key:" & strKey
Dim aSubkeys,retVal ,aTypes
WshShell.RegRead(hkroot & "\" & strKey)
If Err.Number <> 0 Then
If Err.Number = -2147024894 Then
loginfo "Key does not exist:" & strKey
RegistryKeyExists = REGREAD_NOT_EXIST
ElseIf Err.Number = -2147024891 then
'Permissions
logErr "Could not access key. Possibly check permissions:" &
strKey
RegistryKeyExists = Err.Number
Else
loginfo "General:" & Err.Number
RegistryKeyExists = Err.Number
End If
RegistryKeyExists = REGREAD_EXIST
End if
On Error Goto 0
End Function
Sub loginfo(strMsg)
WScript.StdOut.WriteLine(Time & " Info - " & strMsg)
End Sub
Sub logErr(strMsg,boolClear,boolQuit)
WScript.StdOut.WriteLine(Time & " Err - " & strMsg)
If boolQuit Then
WScript.StdOut.WriteLine("Runtime Error details:")
WScript.StdOut.WriteLine("|- " & Err.Number)
WScript.StdOut.WriteLine("|- " & Err.Source)
WScript.StdOut.WriteLine("|- " & Err.Description)
WScript.Quit Err.Number
End if
If boolClear Then Err.Clear
End Sub
_____
-----Original Message-----
From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx]
On Behalf Of MCCARTHY Sean (AXA-TECH-UK)
Sent: 24 September 2010 14:42
To: xxxxxxxxxxxxxxxx
Subject: RE: [gptalk] Restarting servers and automatic updating
I really think I need some looking at this script also, currently in my
environment, I use GPOs to do all this work, but I think I may have missed
something... All my servers only restart when needed, they only apply the
GPOs when needed, but I feel left out and would also like this script ;o)
-----Original Message-----
From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx]
On Behalf Of Darragh O'Shaughnessy
Sent: 24 September 2010 14:08
To: xxxxxxxxxxxxxxxx
Subject: RE: [gptalk] Restarting servers and automatic updating
Yes I had looked at that option in light of this thread but I wanted my
admins to do the updates themselves (especially on database servers etc.). I
have a very simple script that simple notifies and mailbox that a server
requires a reboot.
I implemented it in Vbscript as I wanted it to run natively without and
framework requirements.
I'll post it when I find it. It was only a couple of lines of code
-----Original Message-----
From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx]
On Behalf Of Joe Pochedley
Sent: 24 September 2010 14:00
To: xxxxxxxxxxxxxxxx
Subject: RE: [gptalk] Restarting servers and automatic updating
Darragh,
I've looked at Kevin's script (thanks again, Kevin). It does a nice job of
downloading and applying updates through the Microsoft.Update.Session
object... (Probably exactly what you tried to avoid. ) It also
writes very nice status messages in the event log for success or failure of
the various steps in the process.
If I had one complaint, it's that the script will reboot a machine whether
or not any update truly requires a restart... Of course, 95% of the time,
some update in the pile does require a restart, so it's probably not that
big a deal... But even then there's still 'some' unnecessary rebooting
going on.... Maybe we can combine your registry check with Kevin's script
to only reboot the when it's truly required. That would be ideal.
Look forward to seeing your code!
Joe Pochedley
-----Original Message-----
From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx]
On Behalf Of Darragh O'Shaughnessy
Sent: Friday, September 24, 2010 8:21 AM
To: xxxxxxxxxxxxxxxx
Subject: RE: [gptalk] Restarting servers and automatic updating
Kevin,
I have a vb script that does this (i.e. detects if the server requires
updates) and reboots the server. It does this by checking a registry key. It
only detects updates installed by WU that require a reboot, not manually
installed updates (i.e. updates run outside of the Windows Update Agent
GUI).
I will dig it up and post here as it seems to be much wanted. I'd be
interested in seeing how you accomplished it also? I tried initially using
the API but it didn't appear to expose this readily without creating an
Installation object which is overkill.
Darragh O'Shaughnessy
-----Original Message-----
From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx]
On Behalf Of Shane Williford
Sent: 24 September 2010 13:14
To: xxxxxxxxxxxxxxxx
Subject: RE: [gptalk] Restarting servers and automatic updating
Me three...or ten, whichever number I am!
Shane M. Williford
Systems Administrator
VCP3, MCSE, MCSA Sec, Sec+, Net+, A+
Mazuma Credit Union
Kansas City, MO 64131
xxxxxxxxxxxxxxxx
(816) 361-4194 x6012
-----Original Message-----
From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx]
On Behalf Of Robert K Coffman Jr. -Info From Data Corp.
Sent: Friday, September 24, 2010 7:10 AM
To: xxxxxxxxxxxxxxxx
Subject: Re: [gptalk] Restarting servers and automatic updating
Me too!
- Bob Coffman
On 9/24/2010 2:50 AM, Peter Gough wrote:
> Hi,
>
> I'd like to add another vote to the 'me too' comments. Any chance of
> posting the code?
>
> Many thanks,
>
> Peter
>
> On 22 September 2010 03:08, Doug Neely <xxxxxxxxxxxxxxxx
> <mailto:xxxxxxxxxxxxxxxx>> wrote:
>
> Me too!
>
> *From:* xxxxxxxxxxxxxxxx
> <mailto:xxxxxxxxxxxxxxxx>
> [mailto:xxxxxxxxxxxxxxxx
> <mailto:xxxxxxxxxxxxxxxx>] *On Behalf Of *Derek Rose
> *Sent:* Tuesday, September 21, 2010 10:39 AM
>
>
> *To:* xxxxxxxxxxxxxxxx <mailto:xxxxxxxxxxxxxxxx>
> *Subject:* RE: [gptalk] Restarting servers and automatic updating
>
> Me too
>
> *From:* xxxxxxxxxxxxxxxx
> <mailto:xxxxxxxxxxxxxxxx>
> [mailto:xxxxxxxxxxxxxxxx
> <mailto:xxxxxxxxxxxxxxxx>] *On Behalf Of *Scott Klassen
> *Sent:* Tuesday, September 21, 2010 11:20 AM
> *To:* xxxxxxxxxxxxxxxx <mailto:xxxxxxxxxxxxxxxx>
> *Subject:* RE: [gptalk] Restarting servers and automatic updating
>
> Jumping on the Kevin bandwagon. One more here interested.
>
> Scott Klassen
>
> *From:* xxxxxxxxxxxxxxxx
> <mailto:xxxxxxxxxxxxxxxx>
> [mailto:xxxxxxxxxxxxxxxx
> <mailto:xxxxxxxxxxxxxxxx>] *On Behalf Of *Darragh
> O'Shaughnessy
> *Sent:* Tuesday, September 21, 2010 8:32 AM
> *To:* xxxxxxxxxxxxxxxx <mailto:xxxxxxxxxxxxxxxx>
> *Subject:* RE: [gptalk] Restarting servers and automatic updating
>
> Kevin, I'd like a look at your script too. I wouldn't mind adding
> some simple alert mailing capability to it for our dev teams who
> look after rebooting dev servers when they are patched. You'd save
> me some work! J
>
> Darragh O'Shaughnessy
>
> *From:* xxxxxxxxxxxxxxxx
> <mailto:xxxxxxxxxxxxxxxx>
> [mailto:xxxxxxxxxxxxxxxx
> <mailto:xxxxxxxxxxxxxxxx>] *On Behalf Of *Craig Meyer
> (Hotmail)
> *Sent:* 21 September 2010 14:18
> *To:* xxxxxxxxxxxxxxxx <mailto:xxxxxxxxxxxxxxxx>
> *Subject:* Re: [gptalk] Restarting servers and automatic updating
>
> Just want to say thank you to Kevin for providing me with this script
>
> A very nice piece of work that will be saving me lots of time in
> future.
>
> Thanks Kevin
>
> *From:* Wornell, Kevin (Dallas)
<mailto:xxxxxxxxxxxxxxxx>
>
> *Sent:* Monday, September 20, 2010 3:22 PM
>
> *To:* xxxxxxxxxxxxxxxx <mailto:xxxxxxxxxxxxxxxx>
>
> *Subject:* RE: [gptalk] Restarting servers and automatic updating
>
> I wrote a small VB app that does this in our environment. This app
> basically checks to see if updates are needed based on the WSUS
> server of record, then applies them if needed, and then reboots the
> machine if required. If updates have been previously applied and a
> reboot is needed then it simply reboots the computer. We run this
> as a scheduled task during the maintenance window using GPP files to
> get the exe local and then the task can run it.
>
> I could take a look at stripping out the bits that are specific to
> our environment if you think this would help you.
>
> *Kevin*
>
> * *
>
> *Kevin Wornell**
> *Sr. Technical Engineer
> Towers Watson
> Suite 4100, 500 N. Akard Street | Dallas, TX, 75201
> Phone: 214.530.4057 | Fax: 214.988.5711
> xxxxxxxxxxxxxxxx <mailto:xxxxxxxxxxxxxxxx>
> www.towerswatson.com <http://www.towerswatson.com>
>
> *From:* xxxxxxxxxxxxxxxx
> <mailto:xxxxxxxxxxxxxxxx>
> [mailto:xxxxxxxxxxxxxxxx
> <mailto:xxxxxxxxxxxxxxxx>] *On Behalf Of *Craig Meyer
> (Hotmail)
> *Sent:* Monday, September 20, 2010 4:39 AM
> *To:* xxxxxxxxxxxxxxxx <mailto:xxxxxxxxxxxxxxxx>
> *Subject:* [gptalk] Restarting servers and automatic updating
>
> Hi all
>
> Is it possible to implement a GPO to do the following?
>
> To monitor a group of servers and during a maintenance window (eg
> Sunday morning 1am to 5am) reboot all the Windows Servers that got
> windows updates in the week and require a reboot. In other words all
> those servers with those annoying pop-ups saying updates have been
> installed and they require a reboot?
>
> thanks in advance
>
> /Notice of Confidentiality/
>
> This transmission contains information that may be confidential. It
> has been prepared for the sole and exclusive use of the intended
> recipient and on the basis agreed with that person. If you are not
> the intended recipient of the message (or authorized to receive it
> for the intended recipient), you should notify us immediately; you
> should delete it from your system and may not disclose its contents
> to anyone else.
>
> This e-mail has come to you from Towers Watson Delaware Inc.
>
> CONFIDENTIALITY NOTICE: This e-mail message (including attachments)
> is covered by the Electronic Communications Privacy Act, 18 U.S.C.
> 2510-2521, and is intended only for the person or entity to which it
> is addressed and may contain confidential and/or privileged
> material. Any unauthorized review, use, disclosure, dissemination,
> copying, forwarding or distribution is prohibited. If you are not
> the intended recipient, please contact the sender by reply e-mail
> and destroy all copies of the original message. If you are the
> intended recipient but do not wish to receive communication through
> this medium, please so advise the sender immediately.
>
>
Notice: The information transmitted in this e-mail may contain confidential
and/ or legally privileged information intended only for the use of the
individual(s) named above. Review, use, disclosure, distribution, or
forwarding of this information by persons or entities other than the
intended recipient(s) is prohibited by law and may subject them to criminal
or civil liabilities. Statements and opinion expressed in this e-mail may
not represent those of Mazuma Credit Union. All e-mail communications
through Mazuma's corporate email system are subject to archiving and review
by someone other than the recipient. If you have received this communication
in error, please notify the sender immediately and delete/destroy any and
all copies of the original message from any computer or network system.
This email originates from AXA Technology Services UK Limited (reg.
no. 1854856) which has its registered office at 5 Old Broad Street,
London EC2N 1AD, England.
This message and any files transmitted with it are confidential and
intended solely for the individual or entity to whom they are addressed.
If you have received this in error, you should not disseminate or copy
this email. Please notify the sender immediately and delete this email
from your system.
Please also note that any opinions presented in this email are solely
those of the author and do not necessarily represent those of The AXA
UK Plc Group.
Email transmission cannot be guaranteed to be secure, or error free as
information could be intercepted, corrupted, lost, destroyed, late in
arriving or incomplete as a result of the transmission process. The
sender therefore does not accept liability for any errors or omissions in
the contents of this message which arise as a result of email
transmission.
Finally, the recipient should check this email and any attachments for
viruses. The AXA UK Plc Group accept no liability for any damage
caused by any virus transmitted by this email.
| | | |
|
|