Machines then pull down this image (several hundred times a month), are named/added to the domain, and ready for use. We cannot permit this in our environment, so we have to have Avast installed, but remove these extraneous installations before deploying across our district.Ģ. Note: We have to do it this way, because if we run an Avast installer after imaging a machine, Avast! SafeZone browser icons and Avast! Chrome extensions are installed. We configure Windows and install Avast on a "master" image and activate it, which we then sysprep, and upload to our imaging system. My coworkers and I have come up with some hypotheses, but would like to present all of our information here in the hopes that Avast staff can help us resolve this issue.ġ. We are now experiencing this issue again.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |