| You will not be getting Office 2016 because . . . [message #341347] |
Sat, 08 April 2017 14:47  |
|
|
Originally posted by: J. Clarke
The Powers That Be installed Office 2016 on my work machine a month ago.
Got an email yesterday from the Powers That Be informing me that Office
2016 will not be installed on my work computer because there is an
incompatible piece of software.
I replied "That ship has sailed . . ."
|
|
|
|
| Re: You will not be getting Office 2016 because . . . [message #341351 is a reply to message #341347] |
Sat, 08 April 2017 15:07  |
|
|
Originally posted by: JimP.
On Sat, 8 Apr 2017 14:47:35 -0400, "J. Clarke"
<j.clarke.873638@gmail.com> wrote:
> The Powers That Be installed Office 2016 on my work machine a month ago.
>
> Got an email yesterday from the Powers That Be informing me that Office
> 2016 will not be installed on my work computer because there is an
> incompatible piece of software.
>
> I replied "That ship has sailed . . ."
I've had discussions like that. And got replys from managers asking me
if I was sure. Yeah, couldn't say I could read and write, but I
certainly wanted to.
--
Jim
|
|
|
|
| Re: You will not be getting Office 2016 because . . . [message #341405 is a reply to message #341347] |
Sun, 09 April 2017 10:04 |
jmfbahciv
Messages: 6173
Registered: March 2012
Karma: 0
|
Senior Member |
|
|
J. Clarke wrote:
> The Powers That Be installed Office 2016 on my work machine a month ago.
>
> Got an email yesterday from the Powers That Be informing me that Office
> 2016 will not be installed on my work computer because there is an
> incompatible piece of software.
>
> I replied "That ship has sailed . . ."
>
Or "that chip has sailed..."
Don't TPTBs test things?
/BAH
|
|
|
|
| Re: You will not be getting Office 2016 because . . . [message #341406 is a reply to message #341405] |
Sun, 09 April 2017 10:24 |
|
|
Originally posted by: Whiskers
On 2017-04-09, jmfbahciv <See.above@aol.com> wrote:
> J. Clarke wrote:
>> The Powers That Be installed Office 2016 on my work machine a month ago.
>>
>> Got an email yesterday from the Powers That Be informing me that Office
>> 2016 will not be installed on my work computer because there is an
>> incompatible piece of software.
>>
>> I replied "That ship has sailed . . ."
>>
> Or "that chip has sailed..."
>
> Don't TPTBs test things?
>
> /BAH
Perhaps an IT oik tried to install the software for a second time and
the computer objected that it was 'incompatible' because it was already
installed. It wouldn't surprise me if there was no record of who had
what installed on their personal computers, and little or no restraint
on what users were allowed to install.
--
-- ^^^^^^^^^^
-- Whiskers
-- ~~~~~~~~~~
|
|
|
|
| Re: You will not be getting Office 2016 because . . . [message #341408 is a reply to message #341406] |
Sun, 09 April 2017 10:57 |
|
|
Originally posted by: J. Clarke
In article <slrnoekh18.bl1.catwheezel@ID-107770.user.individual.net>,
catwheezel@operamail.com says...
>
> On 2017-04-09, jmfbahciv <See.above@aol.com> wrote:
>> J. Clarke wrote:
>>> The Powers That Be installed Office 2016 on my work machine a month ago.
>>>
>>> Got an email yesterday from the Powers That Be informing me that Office
>>> 2016 will not be installed on my work computer because there is an
>>> incompatible piece of software.
>>>
>>> I replied "That ship has sailed . . ."
>>>
>> Or "that chip has sailed..."
>>
>> Don't TPTBs test things?
>>
>> /BAH
>
> Perhaps an IT oik tried to install the software for a second time and
> the computer objected that it was 'incompatible' because it was already
> installed. It wouldn't surprise me if there was no record of who had
> what installed on their personal computers, and little or no restraint
> on what users were allowed to install.
No, no IT oik tried to install it.
There is a great deal of restraint on what users are allowed to install.
Officially we aren't supposed to install _anything_. Practically, most
download sites are blocked in the firewall and most users do not have
administrative access--even those with admin don't have registry access
unless they are specifically tasked with installing software, but it is
physically possible to run something that works entirely in userspace.
There do seem to be recordkeeping issues though when installation does not
occur through the default process. There is a procedure for obtaining
nonstandard software but it is apparently the responsibility of the IT oink
who installs it to log it. We didn't get it through the general rollout
and so it may not have gotten logged.
However I wish they had told me what the incompatible software was, it
might be something I'd be just as happy to have an excuse to be rid of.
|
|
|
|
Members
Search
Help
Register
Login
Home
