Hello,
First, I wanted to say you did a wonderful job with the 3.0 release!
Another (very minor) feature request from me... Most of the time (in my case anyway) you execute PSPKI commands from the CA server itself but still you always have to pass to (almost) every command an instance of the CA that you have to previously retrieve through either the machine name or the CA name.
I ended creating a small helper function that retrieve the CA object for the local server and thought it might be useful to others as well.
Even better than a helper function that gets the local instance (which would still be useful in some cases), it would be good that all cmdlets that expect a CertificationAuthority object as input consider no value as the local CA (and throw an exception if the local machine is not a CA of course).
Jordan
Comments: Hmm in our environment we are using dedicated accounts in order to manage the CAs that are only able to log on the CA servers themselves. And then we are using administrative workstations (without any Internet connection, office applications, etc.) and/or a jump server to secure the connection to the server. So in my case remote administration is not an option and is unwanted. Being able to support bulk operations on all CAs in a forest is very nice but in my environment this has never been needed for now. But I understand and respect your position on this.
First, I wanted to say you did a wonderful job with the 3.0 release!
Another (very minor) feature request from me... Most of the time (in my case anyway) you execute PSPKI commands from the CA server itself but still you always have to pass to (almost) every command an instance of the CA that you have to previously retrieve through either the machine name or the CA name.
I ended creating a small helper function that retrieve the CA object for the local server and thought it might be useful to others as well.
Even better than a helper function that gets the local instance (which would still be useful in some cases), it would be good that all cmdlets that expect a CertificationAuthority object as input consider no value as the local CA (and throw an exception if the local machine is not a CA of course).
Jordan
Comments: Hmm in our environment we are using dedicated accounts in order to manage the CAs that are only able to log on the CA servers themselves. And then we are using administrative workstations (without any Internet connection, office applications, etc.) and/or a jump server to secure the connection to the server. So in my case remote administration is not an option and is unwanted. Being able to support bulk operations on all CAs in a forest is very nice but in my environment this has never been needed for now. But I understand and respect your position on this.