Community Tip - Your Friends List is a way to easily have access to the community members that you interact with the most! X
Solved! Go to Solution.
Just from what I am reading, it appears that this is a process where you do not use a "local admin" as the running of the worker daemon service. When you define this service, you will have to use the administrator account that IT provides you which it seems will have a unqiue username and a rotating password. I think your task will have to keep that updated in the service definition. This should be no different than running as a non-admin user. Check out pages below for starting information. You can experiment with this but need to make sure that all parts of the publishing process work as that user running the service.
https://www.ptc.com/en/support/article/CS93677?source=search
https://www.ptc.com/en/support/article/CS335558?source=search
Can you be more specific? The internal Windchill admins and worker users I do not think would apply for this. They would use your LDAP for login. This might be for users running Windchill services or CAD worker login users. From there, I think normal Window account rules would apply.
Our IT department is asking us to "Deploy LAPS and disable the local Administrator account on all servers.". We use Windows Server for Windchill and as many of our CAD workers as we can.
I haven't worked with LAPS before and was wondering if there are any tips, best practices or places that LAPS can't be used with Windchill and CAD Workers.
Just from what I am reading, it appears that this is a process where you do not use a "local admin" as the running of the worker daemon service. When you define this service, you will have to use the administrator account that IT provides you which it seems will have a unqiue username and a rotating password. I think your task will have to keep that updated in the service definition. This should be no different than running as a non-admin user. Check out pages below for starting information. You can experiment with this but need to make sure that all parts of the publishing process work as that user running the service.
https://www.ptc.com/en/support/article/CS93677?source=search
https://www.ptc.com/en/support/article/CS335558?source=search
