Policy Issue with 8.5 Clients (Running on 8.02 Servers)
We have a Desktop Policy, that under the Basics section - Enables AutoSave (every 2mins) & Forces Lock ID after N minutes of activity.(our Domino servers are running on Windows, Domino 8.0.2)
This has been working fine for our Notes 8.0.2 Clients. Since upgrading a few clients to 8.5 ( Both 8.5 Admin Clients & 8.5 Standard Client ) the Desktop policy is no longer enforced or working.
Has anyone seen this issue or similar ), or can suggest a work around a this is currently halting our rollout/planned evaluation of the 8.5 Client.
(I have seen the Inotes Policy posting’s - but we have a mail policy in place also with settings applied )
Is this perhaps an issue because our clients are ‘ahead’ of the Domino server Version? or could we setup an “explicit policy” for our 85 evaluators?
Have you made any changes to your policies or did you just upgrade the client and leave everything else the same?
I would first try running the Policy Synopsis tool in the admin client on the user in question and see if the settings come up correctly there.
If they do then one thing to try would be to open the local address book on the client machine, do control-shift and select the View->Go To menu items and select ($Policies) view. Select all of the documents there and delete them. Then stop the client, restart it, and connect to the home mail server. This should reload all of the policies to the user machines. This will make sure that there can't be any local policy corruption.
If the above does not work, let me know.
Regards,
Mark
Thanks for your response. In answer to your questions …
No we just upgraded the Clients on a few machines, made no changes to the policies except for testing ( see below). Downgrading the Clients again to 8.02 the policies work as required ( Autosave & Lockout ID are the main requirements). After the Client Upgrade I have replaced the design of my mailfile and personal Nab with the local templates, & fully repped with servers.
I should have mentioned initially that all our clients are Roaming so that we have copies of our Nabs up on the home servers, all seems to be repping ok without errors.
Policy Testing - For Testing the Desktop/Setup Policy I altered one of the policies From “Set Value when Modified” to “Set Value & Prevent changes”
What I have noticed is that the Policy is initially “applied” and seems to be working for the first minute but then seems to mysteriously replaced some minutes later with the preferences “greyed out & Switched off - 15mins“ settings I was suspecting whether the roaming is affecting this & was going to see if my profile when not roaming behaves any better. ( I will post back later today on this.)
I have run the Policy Synopsis tool on my account, I seem to be getting the full set of Policies ( if you need me to paste the content let me know)I am not sure what the parameter for eg AutoSave is
I Have deleted all the policies documents in the the $Policies view as instructed. I did notice that when selecting the documents I received various errors “Cannot locate form: PolicyArchive, PolicyMail etc .
Restarting the client the same behaviour occurs – the policy is applied as required and then after a few minutes more the settings are again deselected & greyed out (shows 15mins)
If this helps : The Client Build is IBM Lotus Notes 8.5 Release 8.5 , Revision 20081211.1925 (Release 8.5) Standard Configuration
Ah, the Roaming piece of information was insightful. I'm going to pass this information on a colleague of mine. He fixed some problems where policy information was roaming when it shouldn't have been. I don't know if his changes were purely client based or not and therefore I wonder if having an older server with a newer client present a problem. So I'll contact him regarding your situation.
Regards,
Mark
thanks for your help, Just an update, I have made myself a “Non Roaming” user today and the desktop policy is working as we want it ( ie it autosaves & locks out the ID after 30mins )This setting has ‘stuck’ all day for me.
I will try and add myself back into the roaming tomorrow and see if this then breaks the policy setting again.
It would be useful to know if your colleague can assist, as all of our users are “Roaming” as a default setup (from a support side this gives us less issues when replacing laptops etc) so both desktop policy and roaming functions would be required before we could move ahead to using the 8.5 clients as Standard
The key is the policy documents that get stored locally in your personal NAB. For roaming users, the NAB replicates. The problem that Mark eluded to was that we were getting duplicate policy documents (e.g., multiple Desktop settings docs) in your local NAB because each client would create them and then they would replicate. We fixed that problem before we shipped 8.5.
So please check your Desktop settings document stored in your local NABs on your clients. You can use Doc Properties to look at the values, or copy the necessary forms from pubnames.ntf into your local NAB so you can open those docs directly (that’s why you got those errors, we don’t ship those forms in the personal NAB).
Also, are you roaming between mixed versions of the client (e.g., 8.02 and 8.5)?
I Have put myself back into Roaming today (I am on 8.5 All Clients) and the Desktop policy then doesn’t work (as earlier this week). I had previously created a “notes copy” of my 85 personal nab locally and then renamed it via OS to names.nsf to make sure that I broke any replica ID, I also removed my old roaming folder/dbs from the server( The new personal NAB was initially blanked of docs in the $policies) I allowed Roaming to complete and all my local replicas were repped up to the home mailserver.
What I do see in the $policy view now is two sets of the 6 Company Policies, 1 headed as "Effective policy for: Another user’s name/Organisation ect, the last set headed as PolicyArchive, Policy Desktop etc all have a third view column of "Effective Policy Name, then something like DesktopSet|CN My name, OU xxx O xx etc.
I am not actually roaming across to use other PC’s, but we wouldnt want the client only to be allowed to roam onto the same level client software (ie the slower PC’s are staying with R7 Clients)
hope this helps the investigations - if you need me to mail you anything further, screenshots etc I can be contacted on : john.oconnell@ecosecurities.com
Subject: Same issues with Archive policy and 8.5 client
Hi All,
Regarding your policies issues with LNotes client 8.5, we are encoutering the same.
We have installed 4 Admin Lnotes French 8.5 clients on 7.02 servers. One user (me) has upgraded his mail file to 8.5 french templates, the other users not. They are running 7.02 mail file template.
Since the upgrade, Archiving policies didn’t work.
On the full 8.5 client, clicking the + sign doesn’t expand the link to archive file. On mixed client, clicking the + sign shows the standard local archive, not the one of the policy.
In the policy settings on the client all settings can be changed by user.
I followed the tests done in one of the previous post meaning that I’ve deleted all policies docs from $Policy views and make a LNotes copy of the names.nsf and replaced the existing one with it.
