[ltsb, 1607] Solidworks, %temp% and Software Restriction Policies

[Garacesh]

Scratching my head with this one. With our SRP in place, Solidworks randomly locks up for 2-3 minutes when actions are taken and then eventually does what you've told it to do before locking up again. This goes on in a permanent loop whilst the software is open. With SRP disabled, everything works as normal.

 

I'm having a difficult time because SolidWorks doesn't seem to be creating or accessing any file types that are defined within the SRP. Running Directory Monitor on the entire AppData folder, I find SolidWorks is creating .0001, .fpd, .tmp, .csa, .swp, and .bmp files in AppData/Local/Temp.

 

The issue itself, at a best-guess, seems to revolve around the licensing file. With SRP disabled, SolidWorks creates a %temp%\SolidWorksLicTemp.0001.dir.0000 folder and fills it with the files ~df394b.tmp, ~efe2.tmp, ~defebe.tmp, Ky5s96SF.csa and PfdRun.pfd. It does the same for another folder, %temp%/SolidWorksLicTemp.0001.dir.0001, and everything works fine.

 

With SRP enabled, SolidWorks still creates %temp%\SolidWorksLicTemp.0001.dir.0000 and %temp%\SolidWorksLicTemp.0001.dir.0000, but it only fills them with ~df394b.tmp, ~efe2.tmp and PfdRun.pfd. The program then periodically freezes and keeps creating new SolidWorksLicTemp.0001.dir. folders: 0002, 0003, 0004, 0005, 0006, 0007 etc ad infinitum.

 

I've tried adding an Unrestricted rule for %Temp%\SolicWorksLicTemp*, and that works... Until it doesn't. It worked for about three or four reboots and then just stopped, and we're back to only having the files ~df394b.tmp, ~efe2.tmp and PfdRun.pfd.

[bossman]

@Garacesh

 

Could it be that the path you are allowing access to is different to the one you have stipulated?

 

We have the following path rules in place:

 

%userprofile%\local settings\temp\solidworkslictemp.* - SolidWorks license temp file.

C:\SolidWorks Data\* - To allow users access to the SolidWorks tools addin and Data

%SystemRoot%\temp\TMP* - SolidWorks TMP files in Windows\Temp folder

 

Never had a problem since using it many moons ago...!

[Garacesh]

Hmm.. I did clock the Data folder so I do have C:\SolidWorks Data set as Unrestricted too, but %SystemRoot%\Temp\* set as Disallowed. But even without the SRP, Directory Monitor tells me nothing is happening in C:\Windows\Temp

 

What OS are you doing this with?

 

%UserProfile% resolves as C:\Users\%Username%, and whilst there is a 'Local Settings', it appears to be one of those bad/nonexistent legacy shortcuts

Edited December 11, 2017 by Garacesh

[bossman]

@Garacesh

 

We still using Windows 7 pro atm.... I guess your using Windows 10 which I think Solidworks has issues with...according to many forums and websites...

[Garacesh]

I guess your using Windows 10

That's why we're in the Windows 10 forum

 

Not sure about the issue being W10 itself. The software seems to work fine with the SRP (granted I'm no 3d modelling buff so I can only make a few random shapes and declare it 'working') and they were already using SolidWorks earlier this year before the SRP was implemented. The W10 install was done during the summer, I'd have expected any OS-related issues to have cropped up already.

 

Changing %Temp%\* from Disallowed to Unrestricted results in fully working software, but having %Temp%\* set as Disallowed with an Unrestricted rule for %Temp\SolidWorksLicTemp* and %Temp%\SolidWorksLicTemp*\* results in failures.

 

Upon further testing, changing %Temp%\* to just %Temp% (and leaving the Unrestricted rules in for SolidWorksLicTemp* and SolidWorksLicTemp*\*) still gives me working software. I'm going to keep rebooting and testing to see if it eventually fails again.

 

Have I misunderstood how SRP works? Should I not be ending my SRP rules with \*?

 

Edit: All the examples I found had \* at the end, but in reflection, I'm guessing that's not how it works? I'm assuming if you use \* it's everything in that path regardless of extension, and if it's just folder\ with no asterisk, it's only the designated file types? That would make sense to me but I can't find a solid answer either way.

Edited December 11, 2017 by Garacesh

[bossman]

My Bad Garacesh.... got Ofsted in this morning didn't realise the post was in windows 10 appreciate the humour though......F*ck you!! haha!

[Garacesh]

I really don't get this..

 

2 test users (+ a class full of actual users)

The computers are all in the same OU

The users are all in the same OU.

The same policies are applying to everybody.

The Test Users and actual Users are members of the same security groups.

 

It works for 1 test account consistently.

For everyone else (including the 2nd test account) it fails.

 

the .csa file is there every single time Test Account 1 runs SolidWorks. It's never there when Test Account 2 or any of the actual kids run it.