David,
The batch edit is fine the way you have it. My impression of what it does may be wrong. I was able to use the feature at the start of March while doing an client upgrade on 40 onsite workstations. I needed to enable via BIOS WOL on all machines which I did one by one. Then from my laptop I needed to ensure that I login as the site admin to all 40 workstations. Not at same time by in groups of 5.
So in the example above I had not yet applied the admin repository credential to all workstations in RDM. So I chose to use the batch edit. I thought that in doing the batch edit you would be able to see the change in the individual connections if you were to pick a connection and do an edit. Once I completed the batch edit on the first 5 machines I opened one to edit and I saw that it was not showing that I had linked the connection to a credential entry.
However once I double-clicked the RDP session it worked using the admin credentials I wanted it to use. So the batch edit does work and it did override what was listed which was no credential used originally. I just thought I would actually see what was done via the batch edit override if I were to actually edit a connection to see the properties.
I know the response above was long but I hope it explains what I was expecting to see with a batch edit override.
The batch edit is fine the way you have it. My impression of what it does may be wrong. I was able to use the feature at the start of March while doing an client upgrade on 40 onsite workstations. I needed to enable via BIOS WOL on all machines which I did one by one. Then from my laptop I needed to ensure that I login as the site admin to all 40 workstations. Not at same time by in groups of 5.
So in the example above I had not yet applied the admin repository credential to all workstations in RDM. So I chose to use the batch edit. I thought that in doing the batch edit you would be able to see the change in the individual connections if you were to pick a connection and do an edit. Once I completed the batch edit on the first 5 machines I opened one to edit and I saw that it was not showing that I had linked the connection to a credential entry.
However once I double-clicked the RDP session it worked using the admin credentials I wanted it to use. So the batch edit does work and it did override what was listed which was no credential used originally. I just thought I would actually see what was done via the batch edit override if I were to actually edit a connection to see the properties.
I know the response above was long but I hope it explains what I was expecting to see with a batch edit override.