One. Drive for Business app – silent install. I was struggling with this topic for a while and since there are literally ZERO resources on it on Uncle Google, I thought I will share what I came up with. What I needed: I needed to deploy One. Drive for Business sync app to multiple clients, using automatic approach such as SCCM or group policy, possible as seamless as possible. ![]() An assortment of little pieces of information about using RoboHelp. Stefan 02/06/2014. Thanks for posting this! I’ve been looking for a way to deploy this in our environment. Haven’t tested it yet but looks like a foolproof method. Soy Miguel Guerra, tengo 32 años en el mundo real y más de diez años investigando sobre tecnología web. Soy periodista, creé mi primera página web en 1996 para. Users should not have to do anything at all. My users are using Office 2. I could have just installed Office 2. I needed to retain Office 2. One. Drive for Business 2. What did not work: Standalone One. Drive for Business client available for download from Microsoft site is useless, it is not silent install and it would require users to install it themselves. Creating a custom Office 2. Office customisation tool that only installs One. ![]() Drive was very sketchy. At some point I thought it will work as a silent way. But soon I realised that it was breaking Office 2. Outlook was not working anymore). Users had to “Repair” Office 2. What worked: Using Office Deployment Tool with custom configuration xml file, you need to first download Groove. Retail files then you can run it. Detailed steps below. Steps to create silent installation package for One. Drive for Business. Download Office Deployment Tool http: //www. Unpack exe file, you will end up with a folder with some files, most important is setup. Edit configuration file< Configuration>. Add Source. Path="\\server\share\officedeploy\" Office. Client. Edition="3. Product ID="Groove. Retail" >. < Language ID="en- us" />. Product>. < /Add>. Configuration> Product ID should be Groove. Retail – that is One. Drive for Business (previously Sky. Drive for Business, previously Share. Point Workspace 2. Groove 2. 00. 7…) Client. Edition would be either 3. If you have Office 2. One. Drive 3. 2 bit, 6. Source Path should be a path to your OCT folder, at this stage it does not need to be a network share, it can be just d: \officedeploy\ I will come back to importance of permissions in next steps. Open command prompt or powershell window as Administrator. Navigate to the location of your setup. Run command: setup. Now, Russian roulette starts here, the program will actually not give you any progress or indication anything is happening. Check out sources folder, it should start getting filled with some dlls and other files. Files are being downloaded from the internet. You need to have a Internet connection for this to work. If you are behind a proxy or firewall, e. You may have to bypass corporate proxy or use Internet connection at home. Expected behaviour will be that the program finishes successfully and you will find at list a gigabyte of files in your office deploy folder. That is a half of success. Create a network share for your officedeploy files location. Add necessary permissions for network share – it is important to add everyone to be able to Read the folder. Also, “domain computers” account have to be able to access this share (Read and Execute permissions), because installer actually uses computer account to copy files across during installation. Run \\server\share\officedeploy\setup. One. Drive for Business. This will install One. Drive for Business, you will notice some Office popup in a notification area if you are installing when being on the machine. If something fails, check %temp% for some installation log files. After that finishes you can check if you have One. Drive for Business in Add/Remove programs. You will notice that there is your old Office 2. Office 2. 01. 3 in Programs. This is normal as One. Drive for Business is part of Office 2. Query File Download Plugin for Ajax like, feature rich file downloadsjquery. Download. js Libraryj. Query File Download is a cross server platform compatible j. Query plugin that allows for an Ajax- like file download experience that isn’t normally possible using the web. Features. Brings control back to the developer by exposing a “success. Callback” and “fail. Callback” that allows the developer to control the user experience in either situation. In conjunction with j. Query UI a developer can easily show a modal telling the user that a file download is occurring, disband the modal after the download starts or even inform the user in a friendly manner that an error has occurred. See the Demo for an example of this. File downloads don’t occur in the current window’s location bar. This means if a failure or something unexpected happens the user doesn’t leave the current page they are on or even have to see an ugly error message. This is critical for a good user experience especially on a highly Ajax application. A classic problem with browser file downloads – Error handling. In a general case a file downloads occur after a user clicks an < a href=”location“> link. The href in the instructs the browser to browse to the locationindicated. This is equivalent to setting the window. Java. Script. When the response comes back the HTTP response headers can contain many different things (in fact almost anything). Here are some examples: Normal, HTML Response. Content- Type: text/html; charset=utf- 8. Content- Type: text/html; charset=utf- 8. The above “Content- Type” indicates to the browser that it should parse the DOM in the response and display it to the user. The location in the user’s location bar changes to reflect the address of the just- downloaded content. Normal, “File Download” Response. Content- Disposition: attachment; filename=Report. Content- Disposition: attachment; filename=Report. The above “Content- Disposition” indicates to the browser that the server is trying to invoke a file download in the browser. The browser responds by opening up a file download dialog (or ribbon) for the user to download the file. As a convenience when the browser detects a response like this it doesn’t change the address bar so effectively the user stays on the same page. Failed, “File Download” Response. Content- Type: text/html; charset=utf- 8. Content- Type: text/html; charset=utf- 8. As you may have guessed from that ugly highlighter color we’ve got trouble here. The response from a file download error is generally no different from a normal HTML response, the only difference here is that is has an error message as HTML content. The browser will now happily replace your existing page and address with the new error message. Not only have we now displayed an ugly error message to the user but we have also caused them to leave whatever page they were on. Imagine you have created a nearly exclusively Ajax site like Gmail. A response like this from the server will cause your entire DOM to be replaced by an error message. Imagine this happening to you in Gmail and having to load up everything all over again. Ouch! My current role creating the framework for a highly Ajax application (like Gmail) inspired me to write this plugin for all to use – “web applications” is where the web is going anyways so there has to be a better way…Another classic problem with browser file downloads – “Happy path” user experience. I probably just caught you thinking this: “well so what… my site never has any problems that cause error messages”… fair enough, but consider this: What is the response time of your web site in terms of serving up static files? Is it instantaneous? Is a user going to immediately look in the far corners of their screen for some sort of a spinning indicator or might they get confused or angry based on their technical prowess? Maybe they are looking at one of these? Animation/netscape_anim. I hope not or you’ve got bigger issues)What if you are serving up a dynamically generated file (perhaps a report of SQL data?) based on user input that may take a few seconds. An average user might expect some sort of indication of what is going on. At the very least from a developer’s perspective it’d be nice if it wasn’t easy for them to hammer the download link a few times (to make it faster of course) wasting cycles across an entire n- tiered application. I’ve got a solution… just use Ajax to download it! Good idea! Unfortunately this is not possible due to one key problem: Java. Script, by design, doesn’t have the ability to perform lower level tasks on a users computer out of security concerns. Initiating file download prompts is one of these limitations. You can certainly use an XMLHttp. Request object to download a binary (or otherwise) file but there is nothing you can do to the response to somehow get it saved on the user’s computer. Flash doesn’t have this limitation, but we really don’t want to get into Flash do we? Enter j. Query File Downloadj. Query File Download overcomes all of the aforementioned limitations of a “normal” browser file downloads. Well how the heck does that work? The concept is nothing new in fact: If you browse around the web you will find plenty of forum posts discussing the same technique, I just wasn’t able to find a succinct easy to use plug- in to do it hence my decision to create this plugin. The answer is: An iframe and cookie. What?! I have to rely on Web . Web 2. 0 Ajax application user friendly? Turns out this is the magic bullet combination to work around normal limitations of file downloads, here’s how: iframe. An iframe (which is generally a mortal sin of modern web development) can exist in a DOM but in most respects is treated like an entirely different window. By dynamically inserting a hidden iframe into the DOM and setting its location to the desired file path we can initiate a file download just like it was occurring in the main application window. This directly gets us around one of the nasties of file downloads – if an error occurs the user has now been forced off of the page they were on (which may contain an Ajax application like Gmail) to see an ugly error message. Like a normal file download in the main window an iframe will never fill with content when a successful file download occurs. It simply contains an empty DOM. Well how do we detect what is going on if nothing happens when the file download is successful. Well this is where the cookie comes in: cookie + iframe. Since the creation of cookies exists in HTTP headers, which is standard fare for all web requests and responses, we can actually write a cookie to indicate that a file download has been initiated properly (instead of an error page). The response from the web server will now look something like this. Content- Disposition: attachment; filename=Report. Set- Cookie: file. Download=true; path=/. Content- Disposition: attachment; filename=Report. Set- Cookie: file. Download=true; path=/While we can’t directly tell if a file download has occurred we can check for the existence of a cookie which is exactly how j. Query File Download works. Once a download is initiated on the iframe a configurable duration poll of cookies and the iframe contents occurs. If the iframe fills with contents then we know a file download has occurred (in most cases, make sure to set a MIME type!). If the cookie gets written then we know to stop polling and kill the iframe because the file download dialog/ribbon has been displayed. Using j. Query File Download – Java. Scriptj. Query File Download is easy to use in the simple case but also allows for various callback options as well. Don’t forget to add the required cookie code in the next section! Very simple code demo. Download('/url/to/download. Download('/url/to/download. Use of the very simple approach only protects you from the page changing in the event of a file download error. This alone is pretty useful. If an error occurs the user gets an alert() dialog that says “A file download error has occurred, please try again.” You can see this demoed here under the “Barebones – jquery. Download. js” heading. I wouldn’t recommend using this option given a much better experience is only a few more lines away…Impractical code demo of commonly used features. This just demos what you could do but I’d highly recommend against it unless you want confused and annoyed users. This will result in an alert() dialog telling you a file download initiation has just occurred for the specified URL.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
September 2018
Categories |