Staff-ict

CIao, io ho aggiunto entrambe le voci al task e l’installazione è avvenuta correttamente. Non ho provato senza cmq.

Hello, no news at all…… We ended giving up on this topic due to the deafening silence received from both our ksp company support end this forum. This is a very annoying situation but it is. Best

Sorry but it isn’t. We already have KES11.1.126 actually working on WIn10 v.1903/19H1. What I’d want is the possibility to actually update the build of Win10 by using patch management feature of KSC. It’s the same “job” that the setup.exe inside a Win10 build .iso wuold do, by upgrading the OS in plase, w/o files or apps loss. What I’m wondering is whether it’s possible to achieve the same by usin KSC with some tasks or something like that rather than upgrade client by client using WIn10 .iso Thanks

Hello, KES11.1.1.126 and KSC11.0.0.1131 Thanks

Hello, we are using the “patch management/software updates” feature of ksc (along with a WSUS server) to manage and distribute patches and updates on some of our Windows clients and servers. We’d want to leverage it’s possibilities also for upgrading Win10 clients to a newer build (e.g. from 1803 to 1903) but we cannot because the update process does not even start on the client. Is it possible to achieve this goal?

Hello guys, is there anyone that use KSC11 patch management feature to upgrade Win10 Pro clients to further builds (e.g. from 1803 to 1903, etc..)? I’ve been trying for a while but it’s a pita the management… Thanks.