iManage Work (formerly WorkSite) is a popular document management system commonly used in the legal, accounting, and financial services industries. Historically, there have been issues getting WorkSite to function over DirectAccess, because WorkSite used IPv4 addresses and DirectAccess clients use IPv6. When a DirectAccess client is outside of the office, it communicates with the DirectAccess server using IPv6 exclusively, so applications that make calls directly to IPv4 addresses won’t work.
One way DirectAccess administrators could make WorkSite function was to use portproxy to create v4tov6 address and port mappings on the client. However, this method is error prone, difficult to troubleshoot and support, and doesn’t scale effectively.
The good news is that beginning with release 9, the iManage Work client application has been upgraded to support IPv6. However, it is not enabled by default. To enable IPv6 support for iManage Work, add the following registry key on the client side (not the server!). No other changes are required.
HKLM\Software\Wow6432Node\Interwoven\WorkSite\Server Common\
Type: REG_SZ
String: IP Address Family
Value: IPv6
You can also use the following PowerShell command to add this registry entry.
New-Item -Path “HKLM:\Software\Wow6432Node\Interwoven\WorkSite\Server Common\” -Force
New-ItemProperty -Path “HKLM:\Software\Wow6432Node\Interwoven\WorkSite\Server Common\”-Name “IP Address Family” -PropertyType String -Value IPv6 -Force
After validation testing is complete, deploy the registry setting via Active Directory group policy preferences to all DirectAccess clients and iManage Work will function perfectly over DirectAccess!
Additional Resources
Active Directory Group Policy Preferences on Microsoft TechNet
Bob
/ August 21, 2017You sir are the man, thank you.
Richard M. Hicks
/ August 21, 2017Thanks! Can I assume this tip saved you some aggravation? 🙂
Dan
/ October 13, 2017Richard – there is no server side configuration needed? Does IPv6 need to be enabled on the DMS server (if the Direct Access server is doing IPv6 to IPv4 translation to the internal LAN?).
Richard M. Hicks
/ October 16, 2017No server-side configuration required at all! The change simply enables the client to use the IPv6 address returned by the DirectAccess server’s DNS64 service. 🙂
Dan
/ October 23, 2017Thanks Richard! I’m still struggling with this. Do the Work servers need to have IPv6 addresses configured?
Richard M. Hicks
/ October 23, 2017No, not at all. Feel free to reach out to me directly if you’d like some help. Happy to assist. 🙂
David
/ March 29, 2018Are a top guy Richard, yet again! 🙂
Richard M. Hicks
/ March 29, 2018Thanks David!
Christopher Mann
/ May 9, 2018Richard, after adding the key and string value, it indeed made the connection to Worksite work over DirectAccess. But when my computer is back on the LAN, it cannot connect to the DMS server unless I remove the IP Address Family value and default it back to IPV4
Anyone else seeing this?
Richard M. Hicks
/ May 10, 2018Interesting. That’s not been my experience.
Christopher Mann
/ May 9, 2018I think I answered my own question, if you are only registering your DMS server using the hostname and not the FQDN, you will not be able to connect with the IPv6 value enabled when back on an IPv4 network
Richard M. Hicks
/ May 10, 2018Good to know!