Did anyone use it at all during the 'trial' period? or did end users just at it and walk away?
I love the fact that the company at least was willing to try something - then move to something else.. instead of just being stuck.. it might be costly to do so.. but at least they are working toward a solution they will hopefully like and works well for them.
Yes. It was used by a trial group. But then afterwards, it was never a) forced or b) even pushed on the main users.
For the opensource side. https://www.opsi.org may have something of what you're looking at. I tested it out in the past but SCCM fit with what the management was looking to do.
Just to be clear, I'm not as concerned about the deployment side of things (yet). Do how much is opsi and SCCM: Software Center oriented around end users and how much around administration? I know it should be part of the fabric. I'm just trying to modernize some processes that have been enshrined in the halls of familiarity, and this is the first step for us.
Software Center is almost 100% end user oriented. If you are looking to automate this without hands you wouldn't even expose the interface. I think Opsi is the opposite. I don't think, if I recall, it has any real means for the end users to request applications outside of a really bad web interface... even then I may be mistaken.
That's good to know. I had only done some surface digging into Software Center, and then when I hit the opsi website it looked as you describe it now, so I wanted to be sure that I was communicating clearly. Thanks.
Just looking at this with a customer that just put in a new Windows 2019 server. The machine was purchased with a volume license agreement for Server 2019 Standard. Everything should be super easy, in theory. Problem is, license key from the volume license center doesn't work. We spend a bit of time trying to get this to apply, but no luck.
I have run into a similar situation this morning and not being able activate the VLSC liscense.
Before I decided to call MS and getting frustrated, I was able to activate from an elevated command line.
cscript c:\windows\system32\slmgr.vbs /ipk <product key>
Throwing this out here in case someone comes along this post at a later time.
I've heard that that often works. We had tried that in our case and it had failed.