Office 2013/2016|Office 365|Click2Run [Beta 5.11.6]

[Craig@Invincea]

UPDATED 5/18/2016

**THIS IS HISTORICAL INFO ONLY. THIS HAS ALL BEEN "BAKED" INTO SBIE v.5.11.6 AND ABOVE**

CLICK TO RUN SUPPORT IN SBIE IS ONLY AVAILABLE TO PAID USERS, AS THIS IS A PAID FEATURE
OFFICE 2013 (MOST VERSIONS)
OFFICE 365
OFFICE 2016
OUTLOOK 2013/2016


Add this as a local template in SBIE (NOTE: Baked into beta v5.11.6 already.)

Code: Select all

[Template_Local_Office]
OpenIpcPath=\RPC Control\ClickToRun_Pipeline*

Make sure the " * " is after pipline.

This should increase performance of Office in SBIE.

Just wanted to give a quick update on Click To Run support - Basically Office 2013 (some versions) and all versions of 2016 and Office 365.
We're still testing a few things, I don't want to say when, but very soon.

RELEASED in Beta 5.11.4
Skype for Business is not supported at this time, It's still Lync.exe
OneDrive is supported within Office. Make certain your default web browser in Windows is anything but Edge.

This will be a paid feature - Like Forced Programs/Folders. If you already have a paid license, you're good.

Supported Microsoft Office Products
• Office 2013 (C2R)
• Office 2016
• Office 365
• Outlook 2013
• Outlook 2016
• OneNote 2016
• This includes Word, PowerPoint, Excel, PowerPoint and Publisher.
• Support for “OneDrive” directly from Office (using IE, or another browser other than Edge.)
• Support for “Skype for Business" is not offered. This is still Lync.exe, sporting Skype wallpaper. Lync.exe does not function with SBIE at this time.

Currently not supported to work with Sandboxie:
Windows Apps - Windows 8.1 & Windows 10 “Apps” such as OneNote (app), OneDrive (app) & the Skype** “App” (i.e. Windows Store Apps) are not supported.

There will be a few steps that one will need to do to enable this C2R compatibility..[Only has to be done ONCE, then again if you remove Office]
Link to PDF online http://sandboxie.com/365/office365sbie.pdf
[THESE STEPS ARE NOT NEEDED in Veta v5.11.6]
1. Install Office (if it's not already installed.)
2. Install SBIE version with C2R for Office (5.xx)
3. Open Services.msc in Windows
4. Find the Microsoft Office Click to Run Service - click on it.
5. Right click, and select RESTART.
..This will restart the C2R service with the required SBIE injections.

That's it.

c2rrestart.PNG (73.97 KiB) Viewed 5066 times

Tips:
We Recommend that you Force Office apps to protect you and your email.
Outlook should be set up OUTSIDE of the sandbox first.
Updates to Office suite should be done OUTSIDE of the Sandbox.

[ahut10]

that is so exciting,

whole reason i purchased paid license was to put outlook behind this, and from day one haven't had any luck.

mind you, still enjoying the product with browsers all protected.

thank you in advanced, appreciate the hard work.
and looking forward to using.

regards
Alistair

[Craig@Invincea]

Non Click 2 Run versions of Outlook/Office work just fine (some versions of Office 2013 were not c2r) and versions previous to that do not apply to this update feature.

Only 2013 and newer....Click2Run.

[crssi]

Bought licences (pack of 5), so this should not be a problem.

I really hope you will succeed to support “Skype for Business (Lync.exe)”.

Is this planned for version 5.11?
I can beta test “Skype for Business (Lync.exe)”, if it helps you somehow... just let me know.

Regards

[Craig@Invincea]

C2R Is still being tested. There are some issues that remain that we must look at.

We've tested Skype for business. And the latest release of Office365.

All MS did was rename Skype For Biz. The code and even the launcher is still Lync.exe. Just the GUI and wallpaper is different. It's still Lync at the core.

At this time, that will not work with SBIE.

If MS makes Skype for Biz more like Skype for Windows, then maybe there is a chance...

It's not included in the most recent beta.

[Der Moloch]

I have a question regarding your corporate endpoint software. Do your users have to open Office first and then the document, too, or is this 'inconvenience' exclusive for Sandboxie?

[Craig@Invincea]

There is a lot more customization and logic build into the Endpoint product.... And with that, Comes cost. There are also other items that must be purchased.

Of course, there is far more going into that product, they are locked down on what versions can be used, updates, re-directors, etc.etc.etc. Unlike SBIE, where we try and support multiple versions of X. That is not the case there. Again, Cost.
End Point (older Endpoint) is based on SBIE, not the other way around.

We decided to make this a paid add on feature. For users with EXISTING licenses. We could have just made users pay additional license for ALL current users to recoup the time that has already been dedicated, we decided not to.

As for the "inconvenience" this is how you should be opening documents in SBIE. This was the situation BEFORE Invincea.

The C2R services and related "inconveniences" are because of Microsoft. We have to try and work WITH them.

[bo.elam]

As for the "inconvenience" this is how you should be opening documents in SBIE. This was the situation BEFORE Invincea.

Craig, the way old Office works in older systems is not like that. When I click an XLS or XLSX file, it runs sandboxed automatically using Excel, same opening DOC files, it runs using Word. Power point works alike as well.

For me, using Office in XP and Libre in W7, works similarly, when I click a document, the document runs sandboxed automatically. I don't have to open Office or Libre before opening the document.

Bo

[Craig@Invincea]

Good to know. But, this is what the Devs have recommended in the past. So I'm sticking with their expertise on the work flow. Not saying that opening the doc/docx directly won't work, it probably will. This assures that.

As for "old" Office, unfortunately, we are only supporting 2010 and above - so this is where that may have come from. We haven't been doing any testing on versions previous to that.

Glad to know those still work.

[Craig@Invincea]

As for the "inconvenience" this is how you should be opening documents in SBIE. This was the situation BEFORE Invincea.

Craig, the way old Office works in older systems is not like that. When I click an XLS or XLSX file, it runs sandboxed automatically using Excel, same opening DOC files, it runs using Word. Power point works alike as well.

For me, using Office in XP and Libre in W7, works similarly, when I click a document, the document runs sandboxed automatically. I don't have to open Office or Libre before opening the document.

Bo

Oh, and the "forcing" of programs kicks off a different process/timing to open that program/file in the SB. So if a user has Word, Excel, etc as a forced program, this makes it all the better. Thus, what you've experienced.

However, not every paid user actually uses the forced feature, even though they are paying for it. A lot have no idea.

So we want to make certain that users are able to use Office and not be waiting for the document to load or assuming it's not working in some way.

Buy doing it this way, it assures that. It's noted in the How To doc that will be released that we have some expectation that users know the forced process, and use it if at all possible.

[bo.elam]

Good to know. But, this is what the Devs have recommended in the past. So I'm sticking with their expertise on the work flow. Not saying that opening the doc/docx directly won't work, it probably will. This assures that.

As for "old" Office, unfortunately, we are only supporting 2010 and above - so this is where that may have come from. We haven't been doing any testing on versions previous to that.

Glad to know those still work.

Is nice that Click to run is at least working with Sandboxie now, lets not forget that some months ago was not working at all, so as is now is a nice step forward but I agree with Der moloch, it has to be very inconvenient to have to do manual steps to run Offiice files instead of sandboxing files automatically. I would feel inconvenient. One of the things that I like about Sandboxie and I use for promoting Sandboxie is the action of sandboxing files automatically, with very little thinking required.

By the way, Office 2003 works great with Sandboxie. Since Invincea came over I only had one issue with it, which I reported to Curt via PM, he quickly figured out the change in code that caused the problem and fixed it in the following beta.

Bo

[Craig@Invincea]

Good. Ya, I don't see 2003/2007 changing that much as we go along. Just because we don't actively test on those releases, doesn't mean we won't look at an issue that may come up affecting a lot of users.

[bo.elam]

Oh, and the "forcing" of programs kicks off a different process/timing to open that program/file in the SB. So if a user has Word, Excel, etc as a forced program, this makes it all the better. Thus, what you've experienced.

However, not every paid user actually uses the forced feature, even though they are paying for it. A lot have no idea.

I am not sure Der moloch has the paid version but probably does but I know my good friend cj716 does and would like to force Office files as he did in earlier Window systems, and cant do it.

I am conscious that getting Office to continue working with SBIE in versions 4 and 5 has been tough. I watched the whole process from day one. In the early early betas, I couldn't Force Office at all. When the first beta 4 came out, I couldn't force any Office program and we had to do what they doing now. Open the program and then run the file or use a sandboxed Windows explorer for navigating to the file and run it, that's how things began for all Office versions in SBIE version 4. DDE related issue are extremely hard to fix. After a few betas were released, Office started to work properly.

And I seen the process of getting Office working with SBIE moving forward as time goes on, hopefully it continues that way. And perhaps one day, sandboxing files with Office and Click to run can be done automatically as I do it with Libre in my W7 or old Office in the old XP.

Bo

[Der Moloch]

@Curt

Sorry this came over the wrong way. There was no critique intended, that was why I put "inconvenience" in quotation marks.

[Craig@Invincea]

Oh, and the "forcing" of programs kicks off a different process/timing to open that program/file in the SB. So if a user has Word, Excel, etc as a forced program, this makes it all the better. Thus, what you've experienced.

However, not every paid user actually uses the forced feature, even though they are paying for it. A lot have no idea.

I am not sure Der moloch has the paid version but probably does but I know my good friend cj716 does and would like to force Office files as he did in earlier Window systems, and cant do it.

I am conscious that getting Office to continue working with SBIE in versions 4 and 5 has been tough. I watched the whole process from day one. In the early early betas, I couldn't Force Office at all. When the first beta 4 came out, I couldn't force any Office program and we had to do what they doing now. Open the program and then run the file or use a sandboxed Windows explorer for navigating to the file and run it, that's how things began for all Office versions in SBIE version 4. DDE related issue are extremely hard to fix. After a few betas were released, Office started to work properly.

And I seen the process of getting Office working with SBIE moving forward as time goes on, hopefully it continues that way. And perhaps one day, sandboxing files with Office and Click to run can be done automatically as I do it with Libre in my W7 or old Office in the old XP.

Bo

In testing, you can force Office 2016/Office 365 programs. I was testing word, and Outlook, both set to force..and they work just fine. Faster it appears too... as it's a much cleaner way of starting that program. Forcing any program will seem faster because of the way it does launch.
In talking to Tom yesterday, running the actual Office program first is a good way to avoid problems. Forcing it is even better. You have the force option by default to use Office 2016 and above as it's only available in the paid version.

We're going to highly suggest, at least on the first time...RIGHT after you stop the c2r service that you launch an Office Program (not a file) to have that c2r service restarted with SBIE injection. It's going to be slow the first time. Not only does it have to restart that service, it then has to launch into the SB. So the first go around, we don't want the added possibly issue of something just running a docx file and having that mess up. Otherwise, you're going to have to start it all over again.