Overwriting User Dialog Memory

[NutAce]

Hello All,

We are "decustomizing" our over customized environment we inherited from our previous company.
Basically we are starting from scratch with our Customer Defaults and Templates.

Idea is to have blank templates where ALL the settings are taken from the customer defaults. So far so good.

Problem is now the User Dialog memory. There could be settings in there which are not conforming the Customer Defaults.
Simple example is the Start and End Chamfers of the Threaded hole. I have de-checked them as default in Customer defaults.
However when I start a blank model file and place a threaded hole it still gets the chamfers because that setting has been saved in my dialog memory.

How do I clear for all users the dialog memory to prevent this from happening? Dialog memory is stored on user profile...

Ronald van den Broek
Senior Application Engineer
Winterthur Gas & Diesel Ltd
NX9 / TC10.1.2
HPZ420 Intel(R) Xeon(R) CPU E5-1620 0 @ 3.60GHz, 32 Gb Win7 64B
Nvidea Quadro4000 2048MB DDR5

HP Zbook15
Intel(R) Core(TM) i7-4800MQ
CPU @ 2.70 GHz Win7 64b
Nvidia K1100M 2048 MB DDR5

 

[Xwheelguy]

Did you delete the DialogMemory.dlx file located in your user directory? I'd start there.

Tim Flater
NX Designer
NX 9.0.3.4 Win7 Pro x64 SP1
Intel Xeon 2.53 GHz 6GB RAM
NVIDIA Quadro 4000 2GB

 

[NutAce]

Did you delete the DialogMemory.dlx file located in your user directory? I'd start there.

That is of course no problem...The problem would be to do this automatically for all users.

Ronald van den Broek
Senior Application Engineer
Winterthur Gas & Diesel Ltd
NX9 / TC10.1.2
HPZ420 Intel(R) Xeon(R) CPU E5-1620 0 @ 3.60GHz, 32 Gb Win7 64B
Nvidea Quadro4000 2048MB DDR5

HP Zbook15
Intel(R) Core(TM) i7-4800MQ
CPU @ 2.70 GHz Win7 64b
Nvidia K1100M 2048 MB DDR5

 

[JohnRBaker]

There is an option that can be set which will reset Dialog Memory every time a user exits NX.

John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Digital Factory
Cypress, CA
Siemens PLM:
UG/NX Museum:

To an Engineer, the glass is twice as big as it needs to be.

 

[Toost]

How many users do you have ?
Creating a .bat file which does this deletion among maybe other setup things , is a matter of minutes.
Then email instructions with a link to the bat file to the users ? ( A link because a .bat file might not pass the email security)

Regards,
Tomas

 

[NutAce]

@ John... that would be a bit overkill...it is just for once... We implement the new customer defaults and Templates. Dialog Memory stored before that date should be wiped.

@ Toost... We are talking about some 200 users. From experience we know that mails send to those user only 75% will actually read the e-mail from which only 90% will actually do what is asked...

But indeed I think a bat file will do the trick... We decided on using a powershell script to delete the DialogMemory.dlx from the user folder if it is older than release date for new environment.
We have a number of bat files called with our environment startup so one of them will be used for that.

For those interested... I attached the code...

# Function to remove all files in the given Path that were created before the given date, as well as any empty directories that may be left behind.
function Remove-FilesCreatedBeforeDate([parameter(Mandatory)][ValidateScript({Test-Path $_})][string] $Path, [parameter(Mandatory)][DateTime] $DateTime, [switch] $DeletePathIfEmpty, [switch] $OutputDeletedPaths, [switch] $WhatIf)
{
    Get-ChildItem -Path $Path -Recurse -Force -File | Where-Object { $_.CreationTime -lt $DateTime } | 
		ForEach-Object { if ($OutputDeletedPaths) { Write-Output $_.FullName } Remove-Item -Path $_.FullName -Force -WhatIf:$WhatIf }
    # Remove-EmptyDirectories -Path $Path -DeletePathIfEmpty:$DeletePathIfEmpty -OnlyDeleteDirectoriesCreatedBeforeDate $DateTime -OutputDeletedPaths:$OutputDeletedPaths -WhatIf:$WhatIf
}


# Delete a single file if it is more than 30 minutes old.
# Remove-FilesCreatedBeforeDate -Path "C:\Another\Directory\SomeFile.txt" -DateTime ((Get-Date).AddMinutes(-30))
Remove-FilesCreatedBeforeDate -Path "%USERPROFILE%\Documents\NX\NX90\PROFILE_FILES\DialogMemory.dlx" -DateTime (Get-Date "20/01/2016 00:00 AM")

Ronald van den Broek
Senior Application Engineer
Winterthur Gas & Diesel Ltd
NX9 / TC10.1.2
HPZ420 Intel(R) Xeon(R) CPU E5-1620 0 @ 3.60GHz, 32 Gb Win7 64B
Nvidea Quadro4000 2048MB DDR5

HP Zbook15
Intel(R) Core(TM) i7-4800MQ
CPU @ 2.70 GHz Win7 64b
Nvidia K1100M 2048 MB DDR5

 

[JohnRBaker]

that would be a bit overkill

I agree completely. I was just offering it so as to cover all bases.

John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Digital Factory
Cypress, CA
Siemens PLM:
UG/NX Museum:

To an Engineer, the glass is twice as big as it needs to be.

 

[Toost]

Ronald,
I little trick i was part of implementing at another company,

You let your users use a start script to start NX and Teamcenter,
But, this start script does not start NX and TC, Instead it fetches THE startscript from a local server. ( There should be a fallback if that server doesn't respond.)
This way you can add things to the real startscript on the server, and the user will execute your new settings without knowing the difference.

We rolled out patches and updates this way.
We used Robocopy to copy the files which is "smart" in the sense that if the target files already have been copied to local disk, it does not copy again.
it worked very fine for us, the admins.

Regards,
Tomas

 

[NutAce]

@ Toost,

Tomas, we have a similar process... The TeamCenter start (user side) triggers a script which downloads all environment files (xml,dll etc) and scripts from server (also robocopy) to the local drive, ensuring the user gets the latest updates. If the Server might not respond the procedure continues without the updates.
From there on the startup procedure continues from the local machine.

Ronald van den Broek
Senior Application Engineer
Winterthur Gas & Diesel Ltd
NX9 / TC10.1.2
HPZ420 Intel(R) Xeon(R) CPU E5-1620 0 @ 3.60GHz, 32 Gb Win7 64B
Nvidea Quadro4000 2048MB DDR5

HP Zbook15
Intel(R) Core(TM) i7-4800MQ
CPU @ 2.70 GHz Win7 64b
Nvidia K1100M 2048 MB DDR5