Integrating AutoDomain into an existing implementation
So any thoughts on how to implement autodomain with an existing implementation as now when I assign the AutoDomain fileset to my test machine to simulate our scenario, it says in client Status that SBAdmCom.dll cannot be updated...obviously because it is open.
Also, we want this to be a persistent implementation of AutoDomain; due to the number of laptops and staff rotations etc and the nature of these laptops, we cannot afford to micromanage them...nor can we afford to put 4,000 users on each one any longer wink
RE: Integrating AutoDomain into an existing implementation
Nevermind...I figured that because AutoDomain is a tool for scripted deployment...that if I remove the file from the fileset, perhaps it would work (because we are already deployed). Sure enough, work flawlessly. I will create a full fileset however to create a new client package for future installs.
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.