Tags » Psexec
I recently ran into a situation where a client has a group per server for Administrators, Remote Desktop Users, and hopefully, Service Accounts. This may or may not be the best way of dealing with this, but it does solve a need by moving user access to AD vs configuration on local servers. It’s a little easier to centralize and manage by administrators that may have access to AD but not the servers themselves (eg: HelpDesk users). The problem, as indicated below, is that setting the rights for the service account/groups has been getting done manually to the systems as they are built or needed. This has resulted in inconsistencies, as one might expect. So I found a way to standardize and bring it all “back up to code”, as it were. 1,153 more words
This time I will show you something I use rather often in my day life as well at me work too.
It is a very popular and old method for deploying applications and for sure it is not the best one. 348 more words
(This article has been moved and improved on my self-hosted blog: http://tonybenev.tk/export-current-iis-worker-process-requests-remotely/)
At my regular job I often receive tasks that are very specific and solutions are rare. 247 more words
During my last post I briefly discussed the issues related to the execution context of the chef-client when developing and testing cookbooks. To summarize: on a windows machine the chef-client runs under the context of the local system account, an account which basically is a local admin but has almost no permissions on other Active Directory joined/secured objects ( such as other machines, Active Directory itself or file shares). 421 more words