ndOffice deployment is the process of installing, configuring, and validating the NetDocuments desktop application so users can open, edit, save, version, and profile NetDocuments content from inside Microsoft Word, Excel, PowerPoint, Outlook, and Adobe Acrobat. It is the part of a NetDocuments program your lawyers feel most directly, and it sits inside the wider NetDocuments implementation, which also covers repository design, security, and migration.
What is ndOffice deployment, and why does it decide adoption?
ndOffice deployment is a managed endpoint rollout that places NetDocuments inside the Office applications your users already open every day. Because it runs on every workstation, it touches Office builds, browser policies, single sign-on, security software, and the local disk.
Most of the adoption risk in a NetDocuments program sits here. Users rarely see cabinet design or security groups. They see a save dialog, a check-in prompt, and an Outlook filing pane, and when those fail even 5 percent of the time, people start saving to the desktop. Give ndOffice its own owner, test script, and go-live criteria. For 200 to 500 users, the workstream typically runs four to eight weeks from inventory to the last wave.
How does ndOffice change filing and editing in Microsoft Office?
ndOffice changes filing and editing by replacing local open and save actions with NetDocuments check-out, check-in, and profiling, all from inside the Office ribbon. A user opens a document from NetDocuments, edits it in Word, and saves it back as the current version or a new version without leaving the application.
- Check-out and check-in. Opening a document checks it out to that user, and saving and checking in uploads the changes and releases the lock.
- Versioning. Users either save over the current version or create a new one, and training should state which the firm expects for drafts, redlines, and executed copies.
- Profiling on save. New documents receive client, matter, and document type values as they are saved. Document profiling stays fast when users complete only two or three fields at save, so keep the save dialog short.
ndOffice also supports offline editing, checking the document in automatically on reconnect, and it warns users who open or attach an outdated version.
What should you inventory before an ndOffice rollout?
An ndOffice rollout starts with an inventory of every device type, Office build, browser, and sign-in method your users will run it on. Most failed installs trace back to a configuration nobody listed, so record supported browsers and test single sign-on on both the office network and a home connection, then capture:
- Devices and virtual desktops. Count Windows and macOS machines separately, and flag Citrix or Azure Virtual Desktop users, whose sessions handle local folders differently.
- Office builds and add-ins. List the Office build on each device class and every other add-in loaded in Word and Outlook. Firms commonly run five to ten, and conflicts between them cause many save problems.
- Existing desktop tools. Find older ndOffice or ndClick installs and any legacy DMS add-ins that must be removed. On a move from iManage, the iManage to NetDocuments migration includes retiring the old desktop client once users are live on ndOffice.
How does the ndOffice Echo folder work, and how should you manage it?
The ndOffice Echo folder is a local folder on each workstation that holds documents while they are checked out and being edited. When the user saves and checks a document in, ndOffice uploads the changes to NetDocuments, and until then the latest work exists only on that machine. A separate option, ndOffice Local File Syncing, keeps the latest version of synced documents on the device for offline work and must be enabled by an administrator through a registry setting.
- Location. Keep the default location in the user profile unless endpoint policy requires another approved path, and confirm folder redirection does not move it.
- Check-in discipline. Require users to check in everything before a device swap or profile reset, because an unchecked-in document on a reimaged laptop is lost work.
- Security and retention. Echo folder content is client data on a local disk. Cover it with disk encryption, set a retention period through managed configuration, and add it to your offboarding checklist.
Before anyone renames or moves the Echo folder, every document and email must be checked in and both Office and ndOffice closed; ndOffice rebuilds the folder when it restarts.
How do you set up browser-to-desktop connections for ndOffice?
Browser-to-desktop connections for ndOffice depend on ndOffice running locally and on browser policies that allow the NetDocuments web app to reach it. Current ndOffice versions include the browser integration that once required a separate ndClick install, so most modern deployments no longer push ndClick on its own.
Two checks prevent most failures. First, recent Chrome and Edge releases restrict websites from reaching applications on the local machine, so add the NetDocuments and NetVoyage addresses to your managed browser policy to allow open-in-desktop requests. Second, confirm ndOffice starts at sign-in and stays running, because if it has been closed, browser actions fail with little explanation to the user.
Teach the help desk to separate a browser policy failure from an install, sign-in, or Echo folder problem, since all four look the same to the user.
How should Outlook email filing be handled in an ndOffice rollout?
Outlook email filing should be deployed as a separately tested capability in an ndOffice rollout, with its own pilot cases and its own go-live decision. A bad default can file thousands of messages to the wrong place before anyone notices.
Confirm filed emails pick up the correct client, matter, and document type values, and that suggested locations point at the right workspaces. Then test sending a copy, sending a link, and sharing externally as three separate cases, since NetDocuments DLP can restrict emailing and external sharing of sensitive content. External sharing deserves the extra care, since an analysis of 12,195 confirmed breaches found third-party involvement in breaches doubled to 30 percent.
Many teams switch email integration on one wave after Office integration. Features such as delivery tracking and default message profiling depend on your licensed products and configuration, so confirm them in your own tenant before they reach training materials.
Who should be in an ndOffice pilot group?
An ndOffice pilot group should include 15 to 30 users who represent every role, device type, and location that will run the software.
- Attorneys and assistants. Include heavy drafters, at least two or three partners, and the assistants who file email and manage documents for several attorneys at once.
- Remote and finance users. Cover VPN and home networks, at least one person who regularly works offline, and finance staff who live in Excel with their own add-ins.
- Help desk representatives. Two members of the support team should use ndOffice daily so they learn it before the calls arrive.
Run the pilot for two to three weeks, long enough for offline edits, version conflicts, and month-end email volume to show up.
What should an ndOffice pilot test script cover?
An ndOffice pilot test script should cover every action a user takes, from opening a document to recovering an old version, on each device class. A typical script holds 40 to 60 test cases, each with an expected result and evidence such as a version history screenshot.
- Install and sign-in. Test on each device class, with a target of 95 percent or more successful installs before wider rollout.
- Editing and versions. Open, edit, save, check in, and reopen in Word, Excel, and PowerPoint, then create a new version and restore an earlier one.
- Offline and browser cases. Edit offline, reconnect, and confirm automatic check-in, then open documents in the desktop app from each supported browser.
Add the Outlook filing cases and an Echo folder rebuild. A test that fails on one device class and passes on the others is the most valuable finding a pilot produces.
How should you roll out ndOffice in waves and measure success?
ndOffice should roll out in waves of 50 to 150 users, grouped by office, practice group, or device type, with a short support window after each. Waves let you fix a problem in one group before it reaches the next.
Deploy the approved build through Intune, Configuration Manager, or a similar tool, track failed installs by device, and start the next wave once the previous wave’s ticket count is falling. To measure success, track unclosed check-outs, version conflicts, Echo folder incidents, browser connection errors, and files saved to local drives. A realistic target is 80 to 90 percent of users completing core tasks unassisted within two weeks of their wave.
A central desk makes this workable, because hypercare triage sorts each ticket by cause and routes it to the team that can fix it. Retire legacy desktop tools only after the final wave passes.
Conclusion
ndOffice deployment succeeds when your users stop noticing it. Word opens documents from NetDocuments, saves land in the right matter, email files where it should, and the help desk has a runbook for the few cases that go wrong. Getting there comes from preparation: a full environment inventory, a managed Echo folder, browser policies set before the pilot, and a rollout paced by evidence from each wave.
How Basla can help
Basla provides certified delivery team members for NetDocuments implementation, covering ndOffice deployment planning, environment inventory, pilot test scripting, Outlook filing configuration, help desk runbooks, and post-go-live support. The team works alongside your IT and legal operations staff to run the test cases, document the standard build, and triage issues through each wave, and Basla has doubled legal technology services teams on past programs to meet compressed go-live dates.
Frequently asked questions
What is ndOffice deployment?
ndOffice deployment is the rollout of the NetDocuments desktop application to every workstation so users can open, edit, save, version, and file NetDocuments content from Word, Excel, PowerPoint, Outlook, and Adobe Acrobat.
Does ndOffice still need ndClick?
ndOffice no longer needs a separate ndClick install in most current deployments. Recent ndOffice versions include the browser-to-desktop functionality ndClick used to provide, as long as ndOffice is running and browser policies allow the connection.
What is the ndOffice Echo folder?
The ndOffice Echo folder is a local folder that holds documents while they are checked out and being edited. Changes upload to NetDocuments when the user saves and checks the document in.
How long does an ndOffice rollout take?
An ndOffice rollout for 200 to 500 users typically takes four to eight weeks. That includes one to two weeks of inventory and build, a two to three week pilot, and rollout waves of 50 to 150 users.
Can ndOffice work offline?
ndOffice can work offline, and users can keep editing checked-out documents without a connection. The document is checked in automatically on reconnect, and if the online copy changed meanwhile, both sets of changes are saved as separate versions.
Should Outlook integration go live with Office integration?
Outlook integration usually works best when it goes live one wave after Office integration. That gives users time to learn check-in and check-out first and lets you validate email filing targets.
*This article is provided for general information only and does not constitute legal advice. Basla Solutions provides legal technology implementation and support services and does not practice law.*