Let's all get blindsided together!
-
@coliver said in Let's all get blindsided together!:
@Dashrender said in Let's all get blindsided together!:
@coliver said in Let's all get blindsided together!:
@Dashrender said in Let's all get blindsided together!:
@Jason said in Let's all get blindsided together!:
@Dashrender said in Let's all get blindsided together!:
The bigger issue from my perspective is formatting. I tried converting 7 years ago - formatting was what killed us. Could it have been overcome, sure. But management decided against it.
DOCX XLSX are open standards and pretty much universal across office suites.
That's what I read about opening DOC and XLS files in OpenOffice 7 years ago yet the visual output was nearly useless requiring massive formatting updates.
I can only hope that once things are upgraded to the XML versions that these problems will be left behind.
Nope, doc and xls were a closed format. They didn't translate well because no one had access to the way Microsoft read those formats. Docx and xlsx are XML based and the standard is open. 7 years is a crazy long time in IT... I'm not saying it will be perfect but you will have better luck today then you did in the ancient history you are referring to.
OK I was over simplifying - what I recall was - oh you'll be fine opening DOC and XLX files in OpenOffice (it might have been the year LibreOffice started too) they'll look the same - clearly they were not.
Some basics were generally fine but the official word was that everything would be there but some of the formatting features were implemented differently in oOO and therefore were unsupported.
LOL - it was well over 50% of our documents looked entirely different. It was considered a non starter. And considering things like O365, I'm kinda glad it was.
-
@Dashrender said in Let's all get blindsided together!:
@coliver said in Let's all get blindsided together!:
7 years is a crazy long time in IT... I'm not saying it will be perfect but you will have better luck today then you did in the ancient history you are referring to.
Are you saying that LibreOffice will read the closed format better now than back then? It might be true.
Considering my desire to move to O365 email for $4/month/user, paying $1 more for online access to Office/SharePoint/ODfB is cheap and allows us to use something closer to what people are used to - though it will require some retraining, just like anything does. I suppose the one major advantage that I have in converting everything to XML formats is I could use LibreOffice locally when absolutely required, and the web interface for the rest.
No, I'm saying it can read any new document made since the release of Office 2007. But I think you're right that going to o365 is a really good bet especially if you can push everyone to using office web apps.
-
@coliver said in Let's all get blindsided together!:
@Dashrender said in Let's all get blindsided together!:
@coliver said in Let's all get blindsided together!:
7 years is a crazy long time in IT... I'm not saying it will be perfect but you will have better luck today then you did in the ancient history you are referring to.
Are you saying that LibreOffice will read the closed format better now than back then? It might be true.
Considering my desire to move to O365 email for $4/month/user, paying $1 more for online access to Office/SharePoint/ODfB is cheap and allows us to use something closer to what people are used to - though it will require some retraining, just like anything does. I suppose the one major advantage that I have in converting everything to XML formats is I could use LibreOffice locally when absolutely required, and the web interface for the rest.
No, I'm saying it can read any new document made since the release of Office 2007. But I think you're right that going to o365 is a really good bet especially if you can push everyone to using office web apps.
What do you mean it can read any document made since the release of Office 2007? Unless you're assuming that any document made since the release of Office 2007 was an XML based document?
If that's the case, then that doesn't apply to me. Because we had a smattering of many versions of Office until closer to 2011, I used GP to for all versions of Office to default save as the old doc format. Even after we were converted over to everyone being on Office 2010 or newer, I didn't remove that GP - forgot about it, until 2013. Now all new documents are created in the new format. Unfortunately, a significant number of our 'new' documents are made from old templates, or the previous year's document just with the data deleted, which causes most of them to still be in the old format.
-
@Dashrender said in Let's all get blindsided together!:
I used GP to for all versions of Office to default save as the old doc format. Even after we were converted over to everyone being on Office 2010 or newer, I didn't remove that GP - forgot about it, until 2013. Now all new documents are created in the new format.
Why the heck would you force legacy formats when there were updates for all the older versions that came out when OpenXML came out for them to be able to support them as well.
-
@Jason said in Let's all get blindsided together!:
@Dashrender said in Let's all get blindsided together!:
I used GP to for all versions of Office to default save as the old doc format. Even after we were converted over to everyone being on Office 2010 or newer, I didn't remove that GP - forgot about it, until 2013. Now all new documents are created in the new format.
Why the heck would you force legacy formats when there were updates for all the older versions that came out when OpenXML came out for them to be able to support them as well.
Because @Dashrender is an admitted masochist.
-
It was a choice I made at the time - either manually deploy the update you're talking about, or use GP to do what I did.
Frankly your method didn't occur to me, in retrospect that way would have been more forward thinking, less legacy.
-
Why couldn't the update have just been deployed ?
-
@Jason said in Let's all get blindsided together!:
Why couldn't the update have just been deployed ?
At the time I was unaware of any free deployment software solutions like PDQ Deploy (assuming it was available then) so I was solving a problem that presented itself quickly with a quick solution - GP change.
-
It's an MSI which can be natively deployed with a GPO
-
@Jason said in Let's all get blindsided together!:
It's an MSI which can be natively deployed with a GPO
Thanks bro - that was 8 years ago - not helping me a lot now
