Deploying MS Office 2016 with Munki problems [MOVED from munki-dev]

[Miq Viq]

Are you sure that update packages are enough? 

There seems to be some other stuff like frameworks, fonts and such that are installed with the VL installer. 

I prefer to use the installer that has all the required items in it. 

- MiqViq 

On 11.8.2015, at 20.58, Josh Malone wrote: 

> Well, I can confirm that just deploying the "Updates" along with the captured VL licensing plist is sufficient and works on other hosts that have never touched the VL installer. MS appears to be doing weird things with the VL licensing process under the hood (see bruienne's work in slack #microsoft office) but you don't have to use the VL installer on the clients. 
> 
> BTW, Office 2016 is up to 15.13.1 today. You'll have to deploy the updates anyway - why not start with 'em? 
> 
> -Josh 
> 

> On Tue, Aug 11, 2015 at 1:28 PM, MiqViq wrote: 
> Yes, I tell Munki to ignore the volume licensing pkg and I have added the captured licensing pkg as an update for my two Office 2016 base installers. 
> 
> This second stanza is a partial snip from my pkg receipts. 
> 
> It means the pkg receipt of com.microsoft.pkg.licensing.volume is optional, so Munki will not get confused if it is not installed. 
> 
> I have only launched Word.app once after installing Office 2016 on my test Mac but I would say that installing without com.microsoft.pkg.licensing.volume and adding the license file afterwards _will_ work. 
> 
> But I will continue testing later on this week. And you should probably too do the same... 
> 
> - MiqViq 
> 
> 

> On 11.8.2015, at 18.53, Josh Malone wrote: 
> 
> > So you install from the VL ISO pkg, disable installing the license bits and then install the license bits yourself? 
> > 
> > And what does your second stanza do? 
> > 

- hide quoted text -

> > On Tue, Aug 11, 2015 at 11:47 AM, MiqViq wrote: 
> > This worked for me: 
> > 
> >         <key>installer_choices_xml</key> 
> >         <array> 
> >                 <dict> 
> >                         <key>attributeSetting</key> 
> >                         <integer>0</integer> 
> >                         <key>choiceAttribute</key> 
> >                         <string>selected</string> 
> >                         <key>choiceIdentifier</key> 
> >                         <string>com.microsoft.licensing.volume</string> 
> >                 </dict> 
> >         </array> 
> > 
> > and 
> > 
> >                 <dict> 
> >                         <key>optional</key> 
> >                         <true/> 
> >                         <key>installed_size</key> 
> >                         <integer>12607</integer> 
> >                         <key>packageid</key> 
> >                         <string>com.microsoft.pkg.licensing.volume</string> 
> >                         <key>version</key> 
> >                         <string>15.11.2</string> 
> >                 </dict> 
> > 
> > Modifications in installer_environment had no effect. 
> > 
> > 
> > - MiqViq 
> > 
> > 
> > 
> > 

> > On 11.8.2015, at 18.44, Josh Malone wrote: 
> > 
> > > Even with those scripts that reference $USER, etc.? If this really is a workable option, can you post your XML so I can add it to the wiki as "option c"? 
> > > 

> > > On Tue, Aug 11, 2015 at 11:40 AM, Erik Gomez wrote: 
> > > The volume installer absolutely WILL work with Munki. I'm using it with a ChoiceChangesXML file. 
> > > 
> > > Sent from my iPhone 
> > > 

> > > On Aug 11, 2015, at 10:34 AM, Josh Malone wrote: 
> > > 
> > >> Option B is essentially what I did and works well. The volume licensed installer will NOT work with Munki. 
> > >> 
> > >> Of course, option D should also be employed :) 
> > >> 
> > >> I just started a wiki page for Munki and Office 2016. It would be great if a 365 customer could add documentation on the 365 process. 
> > >> 

> > >> On Tue, Aug 11, 2015 at 7:39 AM, Miq Viq wrote: 
> > >> Thanks for sharing. 
> > >> 
> > >> I think I will go with the plan B. 
> > >> 
> > >> -MiqViq 
> > >> 

- hide quoted text -

> > >>> On 11.8.2015, at 14:37, Erik wrote: 
> > >>> 
> > >>> Miqviq, 
> > >>> 
> > >>> Several of us have worked through the problem in a few ways. 
> > >>> 
> > >>> Option A: 
> > >>> 1. On a VM/test machine, activate it and grab the generated license from /Library/Preferences. 
> > >>> 2. Use a ChoiceChangesXML key in the pkginfo to remove com.microsoft.pkg.licensing_volume from being installed, preventing the loginwindow issue. 
> > >>> 3. Create a package and deploy the licensing file. 
> > >>> 3. Deploy the updated Microsoft packages. 
> > >>> 4. Use LaunchAgent/postinstall to trust the Microsoft AU application. 
> > >>> 
> > >>> Option B: 
> > >>> 1. On a VM/test machine, activate it and grab the generated license from /Library/Preferences. 
> > >>> 2. Deploy the updated Microsoft packages only. 
> > >>> 3. Create a package and deploy the licensing file. 
> > >>> 
> > >>> Option C: 
> > >>> 1. On a VM/test machine, activate it and grab the generated license from /Library/Preferences. 
> > >>> 2. Deploy the current Office 365 package (which contains all current updates and all additional packages, minus com.microsoft.pkg.licensing_volume). 
> > >>> 3. Create a package and deploy the licensing file. 
> > >>> 4. Use LaunchAgent/postinstall to trust the Microsoft AU application. 
> > >>> 
> > >>> Option D: 
> > >>> Complain to Microsoft and let them know they should fix this. 
> > >>> 
> > >>> 
> > >>> No one knows if anything beyond option D is a "support installation". For our testing users, I'm opting for Option A, but I may change my CCXML pkginfo or move to Option B/C as they are faster deployments. 
> > >>> 
> > >>> Hope this helps. If you are anyone has any further questions, please move this to munki-discuss. https://groups.google.com/forum/#!forum/munki-discuss 
> > >>> 
> > >>> On Tuesday, August 11, 2015 at 6:25:10 AM UTC-5, MiqViq wrote: 
> > >>> Hi all, 
> > >>> 
> > >>> anyone else testing MS Office 2016 Volume licensed version deployments? 
> > >>> 
> > >>> My installer running over loginwindow was hanging here: 
> > >>> 
> > >>> Aug 11 13:41:17 installd[1777]: PackageKit: Executing script "./postinstall" in /private/tmp/PKInstallSandbox.kLqkyJ/Scripts/com.microsoft.pkg.licensing.volume.NSHH45 
> > >>> Aug 11 13:41:19 installd[1777]: ./postinstall: _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL. 
> > >>> 
> > >>> And the suspected reason for the problem is in the volume licensing activator pkg (com.microsoft.pkg.licensing.volume). 
> > >>> 
> > >>> It has annoyingly stupid solution in it's postinstall script: 
> > >>> 
> > >>> #!/bin/sh 
> > >>> 
> > >>> logger "Activating Volume License" 
> > >>> volumelicense_exe_path="$2/Microsoft Office Setup Assistant.app/Contents/MacOS/Microsoft Office Setup Assistant" 
> > >>> /usr/bin/sudo -u $USER "$volumelicense_exe_path" 
> > >>> 
> > >>> /bin/rm -rf "$2/Microsoft Office Setup Assistant.app" 
> > >>> 
> > >>> exit 0 
> > >>> 
> > >>> ### 
> > >>> 
> > >>> I am planning to leave out that com.microsoft.pkg.licensing.volume pkg from the base install and fix the license with a separate pkg that installs the license file only. 
> > >>> let's see what happens... 
> > >>> 
> > >>> 
> > >>> -MiqViq 
> > >>> 
> > >>> 
> > >>> -- 
> > >>> Find related discussion groups here: 
> > >>> https://github.com/munki/munki/wiki/Discussion-Group 
> > >>> --- 

[Erik]

I think it's safe although the only way to know for sure is to diff the folders against the 15.11.2 update packages. If you look at the packages, they are incredibly small compared to the update packages. I'm fairly certain the update packages contain all of the fonts/frameworks/etc. With that said though, I still settled on my original option. My assumption is that Microsoft is going to eventually release an updated volume license package and this will give me the right amount of flexibility to change when it comes.

Here are my relevant pkginfo files.

https://gist.github.com/erikng/18a5e49a62e2da7077d9

Attached are the screenshots, icons and banners I'm using as well.

[Harry Fike]

From some discussions on IRC/Slack, one advantage of deploying only the update packages is that Microsoft AutoUpdate is left out. An option I am considering is to deploy the auto updater only to my laptops as a separate package so those users can update themselves.

-- 

Harry

[Erik Gomez]

And if you want to you can simply not install this through a ChoiceChangesXML file as well. 

Sent from my iPhone

--
You received this message because you are subscribed to the Google Groups "munki-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munki-discus...@googlegroups.com.
To post to this group, send email to munki-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/de139a4f-27bd-4a29-8424-5722e100d9e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Harry Fike]

Doing it that way, I'm guessing there is no need to run a script to trust the AU daemon?

-- 

Harry

[Erik Gomez]

Right. No MAU = nothing to trust. 

Sent from my iPhone

--

You received this message because you are subscribed to the Google Groups "munki-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munki-discus...@googlegroups.com.
To post to this group, send email to munki-...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/f0f2b648-ac3a-4689-b9b7-6c02b4c3d742%40googlegroups.com.

[adam cowie]

I am bumping an old thread, because I am now running into issues with deploying a site licensed version of MS Office.  Previously I was attaching a pre licensed version of MS office to my images through System Image Utility.  Since the 10.12.5 update those versions of Office no longer get deployed active.  I have a MS Office Serializer pkg that when I import into munki it shows up in the managed software center however I cannot deploy that.  The MS Office I attach to the image is also a PKG, but that also cannot be deployed through Munki I get the same results.  I should add the department I work for does not purchase the software I receive the files from another department. Any help is appreciated.

[Gregory Neagle]

On Jul 21, 2017, at 9:16 AM, adam cowie <adamm...@gmail.com> wrote:

I am bumping an old thread, because I am now running into issues with deploying a site licensed version of MS Office.  Previously I was attaching a pre licensed version of MS office to my images through System Image Utility.  Since the 10.12.5 update those versions of Office no longer get deployed active.  I have a MS Office Serializer pkg that when I import into munki it shows up in the managed software center however I cannot deploy that.  

Why not?

The MS Office I attach to the image is also a PKG, but that also cannot be deployed through Munki I get the same results.  I should add the department I work for does not purchase the software I receive the files from another department. Any help is appreciated.

On Wednesday, August 12, 2015 at 1:12:58 PM UTC-4, Erik wrote: 

Right. No MAU = nothing to trust. 

Sent from my iPhone

On Aug 12, 2015, at 12:06 PM, Harry Fike <hfi...@gmail.com> wrote:

Doing it that way, I'm guessing there is no need to run a script to trust the AU daemon?

-- 

Harry

--
You received this message because you are subscribed to the Google Groups "munki-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munki-discus...@googlegroups.com.
To post to this group, send email to munki-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/f0f2b648-ac3a-4689-b9b7-6c02b4c3d742%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "munki-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munki-discus...@googlegroups.com.
To post to this group, send email to munki-...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/7f793ab7-1ced-43d2-99f1-b7e04e43a8e3%40googlegroups.com.

[Mike Solin]

Things have changed significantly since this thread was active.  Have you seen Clayton Burlison’s guide to deploying Office 2016 on the Mac?  This really helped me:

https://clburlison.com/demystify-office2016/

Mike

-- 

mi...@mikesolin.com / @flammable
https://mikesolin.com

To view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/7f793ab7-1ced-43d2-99f1-b7e04e43a8e3%40googlegroups.com.

[adam cowie]

The MS Office Serializer shows up in munki and when I got to deploy it to my test machine it say it is unavaliable.  To give you more detail I have tried it by making it a Managed install, and nothing happens.  I also tried a Optional Install.  The Serializer shows up in the Managed Software Center and it says 'Not currently available'

[Gregory Neagle]

On Jul 21, 2017, at 10:40 AM, adam cowie <adamm...@gmail.com> wrote:

The MS Office Serializer shows up in munki and when I got to deploy it to my test machine it say it is unavaliable 

I have no idea what that means. Perhaps post some output from running managedsoftwareupdate, or the relevant section of the log at /Library/Managed Installs/Logs/ManagedSoftwareUpdate.log ?

To view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/5ad11982-100e-452d-9ec2-0801392d30bf%40googlegroups.com.

[adam cowie]

When I run Managed software update the test computer just isn't seeing the Serializer .  Software update log:

Jul 21 2017 13:52:31 -0400 ### Starting managedsoftwareupdate run: manualcheck ###

Jul 21 2017 13:52:31 -0400 Starting...

Jul 21 2017 13:52:31 -0400 ### Beginning managed software check ###

Jul 21 2017 13:52:31 -0400 Checking for available updates...

Jul 21 2017 13:52:31 -0400     Getting manifest MSOFFICE...

Jul 21 2017 13:52:31 -0400     Using manifest: MSOFFICE

Jul 21 2017 13:52:31 -0400     **Checking for installs**

Jul 21 2017 13:52:31 -0400     Getting catalog MSOFFICE...

Jul 21 2017 13:52:31 -0400     GenericDock.mobileconfig version 1.0 (or newer) is already installed.

Jul 21 2017 13:52:31 -0400     K2Client version 7.4.1.1 (or newer) is already installed.

Jul 21 2017 13:52:31 -0400     Need to install Microsoft_Office_2016_VL_Serializer-15.17

Jul 21 2017 13:52:31 -0400     Downloading Microsoft_Office_2016_VL_Serializer.pkg from Microsoft_Office_2016_VL_Serializer.pkg

Jul 21 2017 13:52:31 -0400     Downloading Microsoft_Office_2016_VL_Serializer.pkg from Microsoft_Office_2016_VL_Serializer.pkg

Jul 21 2017 13:52:31 -0400     Downloading Microsoft_Office_2016_VL_Serializer.pkg...

Jul 21 2017 13:52:31 -0400     Bytes received: 330

Jul 21 2017 13:52:31 -0400 WARNING: Download of Microsoft_Office_2016_VL_Serializer-15.17 failed: HTTP result 403: forbidden

Jul 21 2017 13:52:31 -0400     Settings_for_Screen_Lock_Off.mobileconfig version 1.0 (or newer) is already installed.

Jul 21 2017 13:52:31 -0400     **Checking for removals**

Jul 21 2017 13:52:31 -0400     **Checking for managed updates**

Jul 21 2017 13:52:31 -0400 WARNING: Could not process item EPSON Scan-3.9.4.0 for optional install. No pkginfo found in catalogs: MSOFFICE

Jul 21 2017 13:52:31 -0400 WARNING: Could not process item K2Client-7.4.1.0 for optional install. No pkginfo found in catalogs: MSOFFICE

Jul 21 2017 13:52:31 -0400     **Processing self-serve choices**

Jul 21 2017 13:52:33 -0400     Getting icon AppleXeroxPrinterDrivers.png for Xerox Printer Drivers...

Jul 21 2017 13:52:33 -0400     Bytes received: 309

Jul 21 2017 13:52:33 -0400     Getting icon Artlabs.png for Artlabs...

Jul 21 2017 13:52:33 -0400     Bytes received: 292

Jul 21 2017 13:52:34 -0400     Getting icon create_artmac.png for create_artmac...

Jul 21 2017 13:52:34 -0400     Bytes received: 298

Jul 21 2017 13:52:34 -0400     Getting icon Microsoft_Office_2016_VL_Serializer.png for Microsoft_Office_2016_VL_Serializer...

Jul 21 2017 13:52:34 -0400     Bytes received: 320

Jul 21 2017 13:52:34 -0400     Getting icon SuppressMicrosoftExcelFirstRunDialogWindows.mobileconfig.png for Suppress Microsoft Excel First Run Dialog Windows...

Jul 21 2017 13:52:34 -0400     Bytes received: 341

Jul 21 2017 13:52:34 -0400     Getting icon SuppressMicrosoftOneNoteFirstRunDialogWindows.mobileconfig.png for Suppress Microsoft OneNote First Run Dialog Windows...

Jul 21 2017 13:52:34 -0400     Bytes received: 343

Jul 21 2017 13:52:35 -0400     Getting icon SuppressMicrosoftOutlookFirstRunDialogWindows.mobileconfig.png for Suppress Microsoft Outlook First Run Dialog Windows...

Jul 21 2017 13:52:35 -0400     Bytes received: 343

Jul 21 2017 13:52:35 -0400     Getting icon SuppressMicrosoftPowerpointFirstRunDialogWindows.mobileconfig.png for Suppress Microsoft Powerpoint First Run Dialog Windows...

Jul 21 2017 13:52:35 -0400     Bytes received: 346

Jul 21 2017 13:52:35 -0400     Getting icon SuppressMicrosoftWordFirstRunDialogWindows.mobileconfig.png for Suppress Microsoft Word First Run Dialog Windows...

Jul 21 2017 13:52:35 -0400     Bytes received: 340

Jul 21 2017 13:52:36 -0400     Getting client resources...

Jul 21 2017 13:52:36 -0400     Bytes received: 304

Jul 21 2017 13:52:36 -0400     Getting client resources...

Jul 21 2017 13:52:36 -0400     Bytes received: 308

Jul 21 2017 13:52:36 -0400     No change in InstallInfo.

Jul 21 2017 13:52:36 -0400 ###    End managed software check    ###

Jul 21 2017 13:52:36 -0400 Finishing...

Jul 21 2017 13:52:36 -0400 Saving application inventory...

Jul 21 2017 13:52:38 -0400 ### Ending managedsoftwareupdate run ###

[Gregory Neagle]

It's definitely seeing it. It just doesn't have permissions to download it. Check permissions on your web server.

[adam cowie]

Pardon my ignorance... how do I do that?

[Gregory Neagle]

Sorry: I don't know anything about your web server or how it is configured.

Presumably you understand the UNIX permissions model and you can find where the relevant files are stored in the repo...

-Greg

--
You received this message because you are subscribed to the Google Groups "munki-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munki-discus...@googlegroups.com.
To post to this group, send email to munki-...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/dd6f1b8a-7c4d-4f17-8458-3fdd5e4e5967%40googlegroups.com.

[Nick McSpadden]

Adam, how did you set up your Munki server? On a Linux server? Server.app on Mac OS?

On Fri, Jul 21, 2017 at 11:04 AM, Gregory Neagle <gregn...@mac.com> wrote:

Sorry: I don't know anything about your web server or how it is configured.

Presumably you understand the UNIX permissions model and you can find where the relevant files are stored in the repo...

-Greg

On Jul 21, 2017, at 11:03 AM, adam cowie <adamm...@gmail.com> wrote:

Pardon my ignorance... how do I do that?

On Friday, July 21, 2017 at 1:54:47 PM UTC-4, Gregory Neagle wrote:

It's definitely seeing it. It just doesn't have permissions to download it. Check permissions on your web server.

On Jul 21, 2017, at 10:53 AM, adam cowie <adamm...@gmail.com> wrote:

Jul 21 2017 13:52:31 -0400     Need to install Microsoft_Office_2016_VL_Serializer-15.17

Jul 21 2017 13:52:31 -0400     Downloading Microsoft_Office_2016_VL_Serializer.pkg from Microsoft_Office_2016_VL_Serializer.pkg

Jul 21 2017 13:52:31 -0400     Downloading Microsoft_Office_2016_VL_Serializer.pkg from Microsoft_Office_2016_VL_Serializer.pkg

Jul 21 2017 13:52:31 -0400     Downloading Microsoft_Office_2016_VL_Serializer.pkg...

Jul 21 2017 13:52:31 -0400     Bytes received: 330

Jul 21 2017 13:52:31 -0400 WARNING: Download of Microsoft_Office_2016_VL_Serializer-15.17 failed: HTTP result 403: forbidden

--
You received this message because you are subscribed to the Google Groups "munki-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to munki-discuss+unsubscribe@googlegroups.com.

To post to this group, send email to munki-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/dd6f1b8a-7c4d-4f17-8458-3fdd5e4e5967%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "munki-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to munki-discuss+unsubscribe@googlegroups.com.

To post to this group, send email to munki-...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/9F0FD184-44F6-4287-9540-CA74307D499F%40mac.com.

For more options, visit https://groups.google.com/d/optout.

--

--
Nick McSpadden
nmcsp...@gmail.com

[adam cowie]

yes I know UNIX permissions.  It was a permissions issue, and its all resolved now.  I am now able to deploy MS office through Munki.  I am skipping the Serializer since I don't need it.  Although that was a permissions issue.  Thanks for your help

[adam cowie]

Nick its set up through the Server app on Mac OS.  I was able to resolve the issue though.  Thanks.

On Friday, July 21, 2017 at 2:11:26 PM UTC-4, Nick McSpadden wrote:

Adam, how did you set up your Munki server? On a Linux server? Server.app on Mac OS?

On Fri, Jul 21, 2017 at 11:04 AM, Gregory Neagle <gregn...@mac.com> wrote:

Sorry: I don't know anything about your web server or how it is configured.

Presumably you understand the UNIX permissions model and you can find where the relevant files are stored in the repo...

-Greg

On Jul 21, 2017, at 11:03 AM, adam cowie <adamm...@gmail.com> wrote:

Pardon my ignorance... how do I do that?

On Friday, July 21, 2017 at 1:54:47 PM UTC-4, Gregory Neagle wrote:

It's definitely seeing it. It just doesn't have permissions to download it. Check permissions on your web server.

On Jul 21, 2017, at 10:53 AM, adam cowie <adamm...@gmail.com> wrote:

Jul 21 2017 13:52:31 -0400     Need to install Microsoft_Office_2016_VL_Serializer-15.17

Jul 21 2017 13:52:31 -0400     Downloading Microsoft_Office_2016_VL_Serializer.pkg from Microsoft_Office_2016_VL_Serializer.pkg

Jul 21 2017 13:52:31 -0400     Downloading Microsoft_Office_2016_VL_Serializer.pkg from Microsoft_Office_2016_VL_Serializer.pkg

Jul 21 2017 13:52:31 -0400     Downloading Microsoft_Office_2016_VL_Serializer.pkg...

Jul 21 2017 13:52:31 -0400     Bytes received: 330

Jul 21 2017 13:52:31 -0400 WARNING: Download of Microsoft_Office_2016_VL_Serializer-15.17 failed: HTTP result 403: forbidden

--
You received this message because you are subscribed to the Google Groups "munki-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to munki-discus...@googlegroups.com.

To post to this group, send email to munki-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/dd6f1b8a-7c4d-4f17-8458-3fdd5e4e5967%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "munki-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to munki-discus...@googlegroups.com.

To post to this group, send email to munki-...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/9F0FD184-44F6-4287-9540-CA74307D499F%40mac.com.

For more options, visit https://groups.google.com/d/optout.