search

maurice-daly / DriverAutomationTool

Home of the Driver Automation Tool
https://www.msendpointmgr.com
BSD 2-Clause "Simplified" License
393 stars 119 forks source link

Webservice not working with sccm 2010 #178

Open nodiaque opened 3 years ago

nodiaque commented 3 years ago

Hello,

I've updated my SCCM installation last week-end to 2010 and I found out that the webservice doesn't work anymore. I'm not even able to do getwversion, it return nothing. Is there log somewhere of the service itself?

I'm still using that webservice since the rest api version of the invoke-biosdownload doesn't exist and I'm also using the service to add/remove computer in collection during TS.

Thank you

perfectly-preserved-pie commented 3 years ago

I don't think the webservice will work anymore past v4.0:

"Starting with Invoke-CMApplyDriverPackage.ps1 version 4.x and later, the AdminService is the supported method of interface between the script and ConfigMgr."

I mean technically, it says the WebService is not supported, and not that it won't work at all. But that doesn't really inspire confidence.

Why not just use the AdminService API for Drivers and then keep the Webservice for BIOS? That's what we're doing. Coexistence

nodiaque commented 3 years ago

That's is exactly what I have. Driver use the admin service, the bios and other custom script I use have the webservice. But none work anymore since sccm 2010. Like I already said, launching PowerShell and doing command manually all return blank, even getwversion.

I saw bios update script is now 3.0.3 and work with admin service, but still not prime ready. Like for instance, multiple bios for the same machine crash instead of taking the most recent. I'm currently testing it.

I have updated some of my other script to run a remote Ps on the server then run the sccm command, but I liked more the webservice way.