[kkopchynski]

Thanks, I’ll look into the svn thing ASAP. This will be some sort of beta version?

In the instadmg script there is a switch -r to disable chroot. If chroot is the problem would using this switch solve the problem?

[kkopchynski]

I created some test users and did some cross testing. I tested 3 labs. 1 of them had NHR. If a user stays within a lab, there is no configuring of Office when changing machines. This is true with and without NHR. If the user who has been in the NHR lab goes elsewhere, they indeed always reconfigure on any machine in the new lab. I have not returned this user to the NHR lab to see what happens. This is leading me to conclude that it is much more important to have a consistent office installation than to use the Office component of NHR.

The one benefit of NHR may be to reduce the amount of time needed for the reconfiguration. Unfortunately we are also plagued by slow server issues and I cannot easily attribute time differences to NHR. And I need to spend my time getting the installations uniform across campus rather than doing more tests.

[kkopchynski]

FWIW, we just rolled out Network Home Redirect in a lab and it has not gotten any better. But it is hard to separate office issues from AFP network issues in our case. I created an Office custom installer which addresses many of the issues mentioned above and we use that on our image and for any Office re-installs. It has seemed to help compared to the original MS install. It may not address the time stamp issues. Which are the file that need correct time stamps?

Kevin Kopchynski

[Author]

Posts