You assign application but it wont install. I will not repeat other howtos, just point out problems. Group policy accepts only msi files and adds some slipstreams himself. In my experience applications better be published in users gpo or must be assigned in computer gpo. First underwater stone is gpo "Always wait for a network",
you have to apply politics twice because first time when computer starts it don't know it have to wait for a network.
Second mine- enable slow links detection and set to 0, even in good network there could be some timeouts.
Third- time doesnot fit, DC synchronizes time with workstations but only after assigned application has failed, every time. So clocks in domain controller and workstation is not synchronized. So you got Event ID: 1097
Its not so easy, workstation gets time from bios, bios can get it from virtual host machine bios, so applications wants to install before clock is synchronized, you have to disable bios clock or correct it manually, windows usually corrects bios time as well, if not, go in bios and change it, then watch wether bios time is not taken from virtual host. If you realy need to have one time on virtual host and another on virtual client, disable time synchronisation between them.
Fourth mine- path must be dns name of server otherwise it will not use Kerberos authentication, some says- dont browse, type path to msi file manually, I would say browse via network for msi file, workstations recognize hostnames even if you have no wins in network.
MSI file must be well made, otherwise you will get bunch of errors in DC event logs even if all goes fine. Like Event ID: 119
InstallShield can be downloaded 30 day trial, or use some AppDeploy software which makes system snapshots. So you have to fight well before your application is assigned succesfully.
a
Nav komentāru:
Ierakstīt komentāru