* for asset management: itcm have a lot of connectors to other systems (sccm, rvi-plugin for vmware and hyper-v.), sccm have nothing. * itcm: have a web gui sccm have nothing. sccm have the advantage, you can all do over programing interfaces what you want itcm have only a subset of functions coparable to the gui. * automation is possible: itcm uses webservices sccm uses it's own wmi provider and have powershell cmdlets. * on newer sccm versions, sccm deployments are more user centric on itcm there is more device centric (but you can deply sw on userrs, too). there is a addon from fujitsu, that called manage now. * sccm have a build in driver catalog for os installation. main advantage of sccm is only, you can configure a lot of things in the task sequences over the gui. if you have scripting experience, you can the same things do as in sccm. itcm have os installation parameters, that can defined by yourself this parameters can evaluated during installation by a self developed dcript. In itcm: os deployment is not so comfortable as in sccm. on every step you can configure a lot over the gui (for example: partitioning hard disk, apply os image, networkcard configuration, domain join, bitlocker encryption, driver installation, windows update installation, software installation with integrated mdt there is also installation of windows roles and features possible). * for operating system deployment: sccm uses task sequences, this is a order of spcific action task during the os installation.
sccm have only collection or device variables, there is a lot scripting needed, if you would like this. * if you need a lot of installation parameters during installation, itcm is the better choise (packagers can create parameter files, the included parameters can directly replaced during installation).
sccm: installing self developed sw is difficult, if you must done a lot of system configuration (you must buy external sw, for example flexera install shield or admin studio) * if you have a lot of self developed sw: itcm have a build in packager (sxp-packages on windows pif-packager on linux). * sccm: installation of software is only possible, if you create a device collection itcm: you can deploy sw directliy on devices, without create a computer group. so you can easily maintainance the software on device (uninstall, reinstall. * itcm stores the installed packages in the database on every device. * sccm works most with queries and reports installation progress of deployed software can only monitored over reports itcm have a build in job progress monitoring (this is a big advantage, if you have huge deployments). Main difference is the working of booth systems:
0 kommentar(er)
