Jump to content

Recommended Posts

Posted

We encountered an issue earlier, where we copied a PowerPoint onto a laptop's C:\ drive, as it's potentially being used somewhere with no Wi-Fi. To test it would work, we put the laptop into flight mode and attempted to open the PowerPoint. However, it said that it couldn't be opened (I don't have the exact error message atm). Though when we disabled flight mode, it worked immediately. Close it and turn on flight mode - it won't open again.

 

Has anyone else experienced this behaviour?

Posted

Ours used to work with device licensing for about 30 days but I tried it just now while offline and although it says it is licenced it won't let me open or save local files.

 

Microsoft PowerPoint

Sorry, PowerPoint can't read C:\test\test.ppt

 

Works if I open PowerPoint first and then go offline , used to use this for exams so will be interested if there is a solution

Posted
Ours used to work with device licensing for about 30 days but I tried it just now while offline and although it says it is licenced it won't let me open or save local files.

 

Microsoft PowerPoint

Sorry, PowerPoint can't read C:\test\test.ppt

 

Works if I open PowerPoint first and then go offline , used to use this for exams so will be interested if there is a solution

Yeah, this is exactly what we had. I have contacted our reseller regarding the link @midweek provided, I'm just waiting for a reply.

Posted
I asked our reseller (Phoenix) about this and they asked Microsoft who told us it's not available for education. If anyone has it, please let me know as we'd still like it.

Did you try the registry key to see?

  • 2 weeks later...
Posted
Did you try the registry key to see?

I did and unfortunately it didn't resolve the issue*. I currently have a case open with Microsoft and they're looking into it.

 

*The GPO for this (which is actually a GPP setting that looks like a GP setting) actually broke our group policy processing. I noticed that newly imaged devices via SCCM were not communicating with SCCM and picking up the PKI certificate. As it turns out, gpupdate was failing with a "client side error" or something along those line, which meant that the policy to automatically install certificates wasn't applying and thus the client didn't have the PKI certificate to talk to SCCM. As soon as I disabled that GP and performed a gpupdate, they all almost immediately picked up the policies, the PKI certificate and communicated with SCCM.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...