RE: [mssms] Global Condition to determine Office Bitness

2016-10-31 Thread Beardsley, James 
Oh, you’re right. Thanks for the heads up!

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Joe Pochedley
Sent: Thursday, October 27, 2016 3:30 PM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Global Condition to determine Office Bitness

FYI, I have a fresh install of Office 2016 CTR and I don’t have the  
HKLM:\SOFTWARE\Microsoft\Office\15.0\Outlook\Bitness registry property on Win10.

For me, it’s here:

HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Microsoft\Office\16.0\Outlook\Bitness
Or
HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Wow6432Node\Microsoft\Office\16.0\Outlook\Bitness

Anyhow, just wanted to point out you may need to check a few other locations 
for different Windows versions.  HTH

Joe Pochedley
Network & Telecommunications Manager
Fives North American Combustion, Inc.

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Brian Illner
Sent: Wednesday, October 26, 2016 8:13 AM
To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>
Subject: RE: [mssms] Global Condition to determine Office Bitness

Were these all installs onto fresh systems? Or did some have previous versions 
of Office?

We have something similar, but ran into some logic issues as some of the 
upgraded systems still had the old registry key.



BRIAN ILLNER | Canal Insurance Company
864.250.9227
864.679.2537 Fax

[cid:image001.jpg@01D2338B.82714DE0]

Visit canalinsurance.com<http://canalinsurance.com> for news and information.

[cid:image002.jpg@01D2338B.82714DE0]<https://www.linkedin.com/company/canal-insurance-company>
WARNING:  As the information in this transmittal (including attachments, if 
any) may contain confidential, proprietary, or business trade secret 
information, it should only be reviewed by those who are the intended 
recipients.  Unless you are an intended recipient, any review, use, disclosure, 
distribution or copying of this transmittal (or any attachments) is strictly 
prohibited.   If you have received this transmittal in error, please notify me 
immediately by reply email and destroy all copies of the transmittal.  While 
Canal believes this transmittal to be free of virus or other defect, it is the 
responsibility of the recipient to ensure that it is virus free and no 
responsibility is accepted by Canal (or its subsidiaries and affiliates) for 
any loss or damage arising therefrom.
From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Beardsley, James
Sent: Friday, October 21, 2016 8:46 AM
To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>
Subject: RE: [mssms] Global Condition to determine Office Bitness

Nice! Thanks for the tip!

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Ryan
Sent: Thursday, October 20, 2016 2:25 PM
To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>
Subject: Re: [mssms] Global Condition to determine Office Bitness

Fun fact, you don't need the if statement at the end. You could simply have:

($Office15 -eq 'x64') -or ($Office16 -eq 'x64')

That will return $true or $false without needing the If statement.

As to your original question, I have nothing. Just wanted to point this out!


On Thu, Oct 20, 2016 at 1:10 PM Beardsley, James 
<james.beards...@dhgllp.com<mailto:james.beards...@dhgllp.com>> wrote:
Anyone have suggestion or already have a global condition in place that can 
detect if Office 201x is 32-bit or 64-bit? We have a mixed environment of the 
following Office installs and more and more 64-bit installs coming down the 
road, so I’m trying to figure out the best way to detect it programmatically.

Office 2013 ProPlus x86
Office 2013 ProPlus x64
Office 365 (2013) x86
Office 365 (2013) x64
Office 365 (2016) x86
Office 365 (2016) x64

This is what I came up with. I’m trying to determine if this would be accurate 
enough… or is there a better way?

$Office15 = (Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Office\15.0\Outlook" 
-EA SilentlyContinue).Bitness
$Office16 = (Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Office\16.0\Outlook" 
-EA SilentlyContinue).Bitness

If (($Office15 -eq 'x64') -or ($Office16 -eq 'x64')) { Return $true } Else { 
Return $false }

Thanks,

James Beardsley | Digital Technology Services Group
Dixon Hughes Goodman LLP

[cid:8644FC49-D5C9-45AE-B387-04FAFC0CC7A5]<http://www.dhgllp.com/>



Confidentiality Notice: This e-mail is intended only for the addressee named 
above. It contains information that is privileged, confidential or otherwise 
protected from use and disclosure. If you are not the intended recipient, you 
are hereby notified that any review, disclo

RE: [mssms] Global Condition to determine Office Bitness

2016-10-27 Thread Joe Pochedley 
FYI, I have a fresh install of Office 2016 CTR and I don’t have the  
HKLM:\SOFTWARE\Microsoft\Office\15.0\Outlook\Bitness registry property on Win10.

For me, it’s here:

HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Microsoft\Office\16.0\Outlook\Bitness
Or
HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Wow6432Node\Microsoft\Office\16.0\Outlook\Bitness

Anyhow, just wanted to point out you may need to check a few other locations 
for different Windows versions.  HTH

Joe Pochedley
Network & Telecommunications Manager
Fives North American Combustion, Inc.

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Brian Illner
Sent: Wednesday, October 26, 2016 8:13 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Global Condition to determine Office Bitness

Were these all installs onto fresh systems? Or did some have previous versions 
of Office?

We have something similar, but ran into some logic issues as some of the 
upgraded systems still had the old registry key.



BRIAN ILLNER | Canal Insurance Company
864.250.9227
864.679.2537 Fax

[cid:image004.jpg@01D23066.FB3F1AE0]

Visit canalinsurance.com<http://canalinsurance.com> for news and information.

[cid:image006.jpg@01D23066.FB3F1AE0]<https://www.linkedin.com/company/canal-insurance-company>
WARNING:  As the information in this transmittal (including attachments, if 
any) may contain confidential, proprietary, or business trade secret 
information, it should only be reviewed by those who are the intended 
recipients.  Unless you are an intended recipient, any review, use, disclosure, 
distribution or copying of this transmittal (or any attachments) is strictly 
prohibited.   If you have received this transmittal in error, please notify me 
immediately by reply email and destroy all copies of the transmittal.  While 
Canal believes this transmittal to be free of virus or other defect, it is the 
responsibility of the recipient to ensure that it is virus free and no 
responsibility is accepted by Canal (or its subsidiaries and affiliates) for 
any loss or damage arising therefrom.
From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Beardsley, James
Sent: Friday, October 21, 2016 8:46 AM
To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>
Subject: RE: [mssms] Global Condition to determine Office Bitness

Nice! Thanks for the tip!

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Ryan
Sent: Thursday, October 20, 2016 2:25 PM
To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>
Subject: Re: [mssms] Global Condition to determine Office Bitness

Fun fact, you don't need the if statement at the end. You could simply have:

($Office15 -eq 'x64') -or ($Office16 -eq 'x64')

That will return $true or $false without needing the If statement.

As to your original question, I have nothing. Just wanted to point this out!


On Thu, Oct 20, 2016 at 1:10 PM Beardsley, James 
<james.beards...@dhgllp.com<mailto:james.beards...@dhgllp.com>> wrote:
Anyone have suggestion or already have a global condition in place that can 
detect if Office 201x is 32-bit or 64-bit? We have a mixed environment of the 
following Office installs and more and more 64-bit installs coming down the 
road, so I’m trying to figure out the best way to detect it programmatically.

Office 2013 ProPlus x86
Office 2013 ProPlus x64
Office 365 (2013) x86
Office 365 (2013) x64
Office 365 (2016) x86
Office 365 (2016) x64

This is what I came up with. I’m trying to determine if this would be accurate 
enough… or is there a better way?

$Office15 = (Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Office\15.0\Outlook" 
-EA SilentlyContinue).Bitness
$Office16 = (Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Office\16.0\Outlook" 
-EA SilentlyContinue).Bitness

If (($Office15 -eq 'x64') -or ($Office16 -eq 'x64')) { Return $true } Else { 
Return $false }

Thanks,

James Beardsley | Digital Technology Services Group
Dixon Hughes Goodman LLP

[cid:8644FC49-D5C9-45AE-B387-04FAFC0CC7A5]<http://www.dhgllp.com/>



Confidentiality Notice: This e-mail is intended only for the addressee named 
above. It contains information that is privileged, confidential or otherwise 
protected from use and disclosure. If you are not the intended recipient, you 
are hereby notified that any review, disclosure, copying, or dissemination of 
this transmission, or taking of any action in reliance on its contents, or 
other use is strictly prohibited. If you have received this transmission in 
error, please reply to the sender listed above immediately and permanently 
delete this message from your inbox. Thank you for your cooperation.




Confi

RE: [mssms] Global Condition to determine Office Bitness

2016-10-26 Thread Brian Illner 
Were these all installs onto fresh systems? Or did some have previous versions 
of Office?

We have something similar, but ran into some logic issues as some of the 
upgraded systems still had the old registry key.



BRIAN ILLNER | Canal Insurance Company
864.250.9227
864.679.2537 Fax

[cid:image001.jpg@01D22F60.CAA43250]

Visit canalinsurance.com<http://canalinsurance.com> for news and information.

[cid:image002.jpg@01D22F60.CAA43250]<https://www.linkedin.com/company/canal-insurance-company>
WARNING:  As the information in this transmittal (including attachments, if 
any) may contain confidential, proprietary, or business trade secret 
information, it should only be reviewed by those who are the intended 
recipients.  Unless you are an intended recipient, any review, use, disclosure, 
distribution or copying of this transmittal (or any attachments) is strictly 
prohibited.   If you have received this transmittal in error, please notify me 
immediately by reply email and destroy all copies of the transmittal.  While 
Canal believes this transmittal to be free of virus or other defect, it is the 
responsibility of the recipient to ensure that it is virus free and no 
responsibility is accepted by Canal (or its subsidiaries and affiliates) for 
any loss or damage arising therefrom.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Beardsley, James
Sent: Friday, October 21, 2016 8:46 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Global Condition to determine Office Bitness

Nice! Thanks for the tip!

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Ryan
Sent: Thursday, October 20, 2016 2:25 PM
To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>
Subject: Re: [mssms] Global Condition to determine Office Bitness

Fun fact, you don't need the if statement at the end. You could simply have:

($Office15 -eq 'x64') -or ($Office16 -eq 'x64')

That will return $true or $false without needing the If statement.

As to your original question, I have nothing. Just wanted to point this out!


On Thu, Oct 20, 2016 at 1:10 PM Beardsley, James 
<james.beards...@dhgllp.com<mailto:james.beards...@dhgllp.com>> wrote:
Anyone have suggestion or already have a global condition in place that can 
detect if Office 201x is 32-bit or 64-bit? We have a mixed environment of the 
following Office installs and more and more 64-bit installs coming down the 
road, so I’m trying to figure out the best way to detect it programmatically.

Office 2013 ProPlus x86
Office 2013 ProPlus x64
Office 365 (2013) x86
Office 365 (2013) x64
Office 365 (2016) x86
Office 365 (2016) x64

This is what I came up with. I’m trying to determine if this would be accurate 
enough… or is there a better way?

$Office15 = (Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Office\15.0\Outlook" 
-EA SilentlyContinue).Bitness
$Office16 = (Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Office\16.0\Outlook" 
-EA SilentlyContinue).Bitness

If (($Office15 -eq 'x64') -or ($Office16 -eq 'x64')) { Return $true } Else { 
Return $false }

Thanks,

James Beardsley | Digital Technology Services Group
Dixon Hughes Goodman LLP

[cid:8644FC49-D5C9-45AE-B387-04FAFC0CC7A5]<http://www.dhgllp.com/>



Confidentiality Notice: This e-mail is intended only for the addressee named 
above. It contains information that is privileged, confidential or otherwise 
protected from use and disclosure. If you are not the intended recipient, you 
are hereby notified that any review, disclosure, copying, or dissemination of 
this transmission, or taking of any action in reliance on its contents, or 
other use is strictly prohibited. If you have received this transmission in 
error, please reply to the sender listed above immediately and permanently 
delete this message from your inbox. Thank you for your cooperation.




Confidentiality Notice: This e-mail is intended only for the addressee named 
above. It contains information that is privileged, confidential or otherwise 
protected from use and disclosure. If you are not the intended recipient, you 
are hereby notified that any review, disclosure, copying, or dissemination of 
this transmission, or taking of any action in reliance on its contents, or 
other use is strictly prohibited. If you have received this transmission in 
error, please reply to the sender listed above immediately and permanently 
delete this message from your inbox. Thank you for your cooperation.

RE: [mssms] Global Condition to determine Office Bitness

2016-10-21 Thread Beardsley, James 
Nice! Thanks for the tip!

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Ryan
Sent: Thursday, October 20, 2016 2:25 PM
To: mssms@lists.myitforum.com
Subject: Re: [mssms] Global Condition to determine Office Bitness

Fun fact, you don't need the if statement at the end. You could simply have:

($Office15 -eq 'x64') -or ($Office16 -eq 'x64')

That will return $true or $false without needing the If statement.

As to your original question, I have nothing. Just wanted to point this out!


On Thu, Oct 20, 2016 at 1:10 PM Beardsley, James 
<james.beards...@dhgllp.com<mailto:james.beards...@dhgllp.com>> wrote:
Anyone have suggestion or already have a global condition in place that can 
detect if Office 201x is 32-bit or 64-bit? We have a mixed environment of the 
following Office installs and more and more 64-bit installs coming down the 
road, so I’m trying to figure out the best way to detect it programmatically.

Office 2013 ProPlus x86
Office 2013 ProPlus x64
Office 365 (2013) x86
Office 365 (2013) x64
Office 365 (2016) x86
Office 365 (2016) x64

This is what I came up with. I’m trying to determine if this would be accurate 
enough… or is there a better way?

$Office15 = (Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Office\15.0\Outlook" 
-EA SilentlyContinue).Bitness
$Office16 = (Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Office\16.0\Outlook" 
-EA SilentlyContinue).Bitness

If (($Office15 -eq 'x64') -or ($Office16 -eq 'x64')) { Return $true } Else { 
Return $false }

Thanks,

James Beardsley | Digital Technology Services Group
Dixon Hughes Goodman LLP

[cid:8644FC49-D5C9-45AE-B387-04FAFC0CC7A5]<http://www.dhgllp.com/>



Confidentiality Notice: This e-mail is intended only for the addressee named 
above. It contains information that is privileged, confidential or otherwise 
protected from use and disclosure. If you are not the intended recipient, you 
are hereby notified that any review, disclosure, copying, or dissemination of 
this transmission, or taking of any action in reliance on its contents, or 
other use is strictly prohibited. If you have received this transmission in 
error, please reply to the sender listed above immediately and permanently 
delete this message from your inbox. Thank you for your cooperation.




Confidentiality Notice: This e-mail is intended only for the addressee named 
above. It contains information that is privileged, confidential or otherwise 
protected from use and disclosure. If you are not the intended recipient, you 
are hereby notified that any review, disclosure, copying, or dissemination of 
this transmission, or taking of any action in reliance on its contents, or 
other use is strictly prohibited. If you have received this transmission in 
error, please reply to the sender listed above immediately and permanently 
delete this message from your inbox. Thank you for your cooperation.

Re: [mssms] Global Condition to determine Office Bitness

2016-10-20 Thread Ryan 
Fun fact, you don't need the if statement at the end. You could simply have:

($Office15 -eq 'x64') -or ($Office16 -eq 'x64')

That will return $true or $false without needing the If statement.

As to your original question, I have nothing. Just wanted to point this out!


On Thu, Oct 20, 2016 at 1:10 PM Beardsley, James 
wrote:

> Anyone have suggestion or already have a global condition in place that
> can detect if Office 201x is 32-bit or 64-bit? We have a mixed environment
> of the following Office installs and more and more 64-bit installs coming
> down the road, so I’m trying to figure out the best way to detect it
> programmatically.
>
>
>
> Office 2013 ProPlus x86
>
> Office 2013 ProPlus x64
>
> Office 365 (2013) x86
>
> Office 365 (2013) x64
>
> Office 365 (2016) x86
>
> Office 365 (2016) x64
>
>
>
> This is what I came up with. I’m trying to determine if this would be
> accurate enough… or is there a better way?
>
>
>
> $Office15 = (Get-ItemProperty
> "HKLM:\SOFTWARE\Microsoft\Office\15.0\Outlook" -EA SilentlyContinue).
> Bitness
>
> $Office16 = (Get-ItemProperty
> "HKLM:\SOFTWARE\Microsoft\Office\16.0\Outlook" -EA SilentlyContinue).
> Bitness
>
>
>
> If (($Office15 -eq 'x64') -or ($Office16 -eq 'x64')) { Return $true } Else
> { Return $false }
>
>
>
> Thanks,
>
>
>
> *James Beardsley |* Digital Technology Services Group
>
> Dixon Hughes Goodman LLP
>
>
>
> [image: cid:8644FC49-D5C9-45AE-B387-04FAFC0CC7A5] 
>
>
> --
>
> *Confidentiality Notice:* This e-mail is intended only for the addressee
> named above. It contains information that is privileged, confidential or
> otherwise protected from use and disclosure. If you are not the intended
> recipient, you are hereby notified that any review, disclosure, copying, or
> dissemination of this transmission, or taking of any action in reliance on
> its contents, or other use is strictly prohibited. If you have received
> this transmission in error, please reply to the sender listed above
> immediately and permanently delete this message from your inbox. Thank you
> for your cooperation.
>
>