I have a big problem with Desktop Policy to push out notes.ini settings to the clients.
Server is 8.5.1 and also clients.
I have created a Desktop policy that includes severeal notes.ini settings that are supposed to be pushed out to the clients.
Example:
DATEORDER=YMD
TIMESEPARATOR=:
DATESEPARATOR=-
We have double checked this settings several times from the start when we put it in, and also several times afterward.
BUT on the client it shows as:
DATEORDER=YMD
TIMESEPARATOR=:
DATESEPARATOR=0
That is DATESEPARATOR=0 !!?! and users are complainging because date is
2010003031 - which bring chaos to the whole organization.
This is probably a bug and it is new to me.
Anyone with an idea how to remove this from users notes.ini? I really need help to fix this one.
Subject: Not Supported
I believe that these parameters are obsolete as of R6
Subject: Correct
This is correct for Windows machines. But on linux these have to be used to get international standard for dates.
Linux client shows
03/21/2010
But with these parameters
2010-03-21
This is the TECHNOTE:
DateOrder and DateSeparator notes.ini parameters do not work as expected in Notes/Domino 6
http://www-01.ibm.com/support/docview.wss?rs=899&uid=swg21195319
Subject: Partly solved
I updated the policy with:DateSeparator=/
And this setting was correctly pushed out the clients. A “/” is not as optimal compared to a “-”, but it’s way better than a faulty “0” as date separator.
Conclusion is:
Do not put in notes.ini-variables through policy if there is not an alternative value to use, because notes.ini-policy cannot be reverted, only updated at best.
Subject: Not to beat a dead horse…
First of all, I’m glad you got your issue partly solved!
That having been said, I am (much) less than enthusiastic with the recent versions of Domino and Lotus Notes. ‘Features’ such as this, that are broken, and apparently will never be fixed are very frustrating to clients and admins alike.
I’ve now got 11 or 12 issues that I’ve been living with since 8.0 - All PMRs closed ‘No plans to fix’ - and that just blows my mind. We’re trying to upgrade from 6.5.5 to a current version, but the 6.5.5 client works, and the 8.x client is buggy as hell and keeps getting worse. Policies, Welcome Page issues, Doclinks, DDM, Journaling, and here i go getting all worked up again.
Maybe because I just spent another 4 hours cleaning up after another problem.
I sure chose the wrong profession.
Subject: Cannot remove Notes.ini settings per Support
I have a ticket open with Support right now - While testing an 8.5.1 rollout, I found that I can push Notes.ini settings out to users using a Policy, but the same settings cannot be removed via Policy.
Support is telling me that once settings are pushed out, the only way to remove them is to send the user a button agent to update the Notes.ini.
I’m curious to know, then, what the ‘Remove’ and ‘Remove All’ buttons are for - no response as of yet.
Subject: there are 2 issues with this problem
first , once you push something to the notes.ini it is not possible to remove it. And When you will read the 2nd issue, you will understand that this feature is something that we cannot expect before 10 years !
2nd one: even is you remove the parameter from the policy, it still exist in the policy and you MUST do an agent yourself to clean the policy !! I had a PMR for this and here is the answer I have from the support, just crazy for me
This PMR has been passed to me in the next level of Lotus Support.
When you delete a field from a Form in the Domino Designer client, this will not remove the field from any document based on this Form in the database. If you look at the ‘Fields’ tab (second tab) of the Document Properties and you will see that Fields that you previously defined.
In order to delete these fields you will need to create a ‘Formula’ Agent and set to run on selected documents.
FIELD FieldName:=@DeleteField;
Where FieldName is the name of the field that you created.
Once you have deleted this field this will not remove any settings that have already been pushed down to the Notes clients, but will prevent further Notes client from getting this field set.
And when I asked him, if a fix is schedule for this :
Unfortunately this will not be fixed as this is the way that the Domino Database structure works. If a field is removed from a Form then the underlying data structure as not changed. This does mean that if a field is accidentally deleted that the data is not deleted. A form is only use as a means of inputting and displaying the data in a document and not the contents of the document itself.
just crazy…
Subject: I agree 100%
The more I try to make my life easier using Policies, the harder my life becomes.
Unfortunately, so many of the Lotusscript methods have never been fixed, and I was hoping that using Policies was an alternative.