Yep. Remember, clients have no concept of what collections they are a member of. The site assigns/deploys things to them based on their membership, but the client simply knows that it is assigned/deployed to them and thus cannot interpret those assignments/deployments in the context of which collection they are applicable to.
J From: [email protected] [mailto:[email protected]] On Behalf Of Ryan Sent: Tuesday, August 19, 2014 9:42 AM To: [email protected] Subject: Re: [mssms] collection variable applied to one collection leaking over into another collection Collection variables go with the device not the deployment. Any collections with variables the device is in will be set in OSD. On Tue, Aug 19, 2014 at 9:31 AM, Jimmy Martin <[email protected]<mailto:[email protected]>> wrote: Hi, • Zti task sequence deployed to a collection • Only 1 task sequence variable on collection defined and that is to skip the hta • In zti task sequence, usmtlocal=true is set b4 userstate and logs show it understands that • Smsts then shows it trying to connect to a unc that was defined on another collection the computer is a member of defining osdstatestorepath Is this appropriate behavior? I was thinking collection variables would only subject the collection to the variable being set… Jimmy Martin | Engineer | Information Technology | BMHCC - CORPORATE Phone: (901) 227-8209<tel:%28901%29%20227-8209> | [email protected]<mailto:[email protected]> Opinions expressed above are not necessarily those of Baptist. This message and any files transmitted with it may contain legally privileged, confidential, or proprietary information. If you are not the intended recipient of this message, you are not permitted to use, copy, or forward it, in whole or in part without the express consent of the sender. Please notify the sender of the error by reply email, disregard the foregoing messages, and delete it immediately. P Please consider the environment before printing this email...
