Also I have Queried in database "select * from v_CollectionVariable"  not
showing anything. But how the Task sequence variables are showing up in
client machiens am not getting

On Thu, Mar 16, 2017 at 11:44 AM, Kevin Ray <[email protected]> wrote:

> Task Sequence Variables not showing on collection Properties but when im
> trying to image a machine , In Task sequence Wizard showing the Variables ..
>
> Its strange to me [image: 🤔][image: 🤔][image: 🤔][image: 😨][image: 😨][image:
> 😨][image: 😨][image: 😨]
>
> On Thu, Mar 16, 2017 at 11:18 AM, Kevin Ray <[email protected]>
> wrote:
>
>> Hi all,
>>
>> i'm wondering ,  unable to see my Task sequence variables on "All Unknown
>> machines collection " I used  below method to create.
>>
>> https://www.windows-noob.com/forums/topic/5542-how-can-i-eas
>> ily-prompt-for-a-computer-name-in-configuration-manager-2012/
>>
>> *remove the checkmark from Do Not Display this value in the Configuration
>> Manager console --- *
>>
>>
>> I would like to remove the TS Variables .. Any help please
>>
>> [image: Inline image 1]
>>
>> On Sun, Mar 5, 2017 at 10:40 PM, Marable, Mike <[email protected]>
>> wrote:
>>
>>> With UI++ you could create a pull-down list of OUs for the person
>>> building the machine to select from.
>>>
>>>
>>>
>>> *From: *<[email protected]> on behalf of Kevin Ray <
>>> [email protected]>
>>> *Reply-To: *"[email protected]" <[email protected]>
>>> *Date: *Sunday, March 5, 2017 at 2:40 PM
>>> *To: *"[email protected]" <[email protected]>
>>> *Subject: *Re: [mssms] OSD builds required to ask machine names
>>>
>>>
>>>
>>> Thanks Mike.Its seems to be cool without adding much efforts.. How about
>>> if want to provide AD OU option to choose for user.. How i can do that
>>>  ?any help please
>>>
>>>
>>>
>>> On Sun, Mar 5, 2017 at 9:44 AM, Marable, Mike <[email protected]>
>>> wrote:
>>>
>>> You can do this very easily actually.  You just need to populate the
>>> variables, and you have several options for doing that.
>>>
>>>
>>>
>>> Niall wrote a posting a while back that you can use to get things
>>> started.
>>>
>>> https://www.windows-noob.com/forums/topic/5542-how-can-i-eas
>>> ily-prompt-for-a-computer-name-in-configuration-manager-2012/
>>>
>>>
>>>
>>> It’s not fancy but it’s simple and an excellent way to start.  I’d start
>>> with this first.
>>>
>>>
>>>
>>> Of course, you can write a simple HTA to prompt or even better you can
>>> try UI++ (http://home.configmgrftw.com/uiplusplus/ ).  This is an
>>> excellent tool for prompting for user input during a task sequence.
>>>
>>>
>>>
>>> If it were me, I’d start with Niall’s method first.  It’s simple and
>>> very easy to implement.  Then after that’s working tackling UI++ to replace
>>> the collection variable prompts with a GUI front-end with UI++.
>>>
>>>
>>>
>>> Mike
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *From: *<[email protected]> on behalf of Kevin Ray <
>>> [email protected]>
>>> *Reply-To: *"[email protected]" <[email protected]>
>>> *Date: *Sunday, March 5, 2017 at 7:55 AM
>>> *To: *"[email protected]" <[email protected]>
>>> *Subject: *[mssms] OSD builds required to ask machine names
>>>
>>>
>>>
>>> Hi All
>>>
>>>
>>>
>>> I have created a task sequence for unknown supports .machines are
>>> created successfully.
>>>
>>>
>>>
>>> Now i would go further my requirement , for same task sequence(not used
>>> MDT integration. But if requires i can integrete it) while starting the
>>> image its requires to ask for user to provide the machine_name and AD OU
>>> name....
>>>
>>>
>>>
>>> I hope we can achieve this UDI wizard,but can any one please guild me
>>> for any step by step example please or any otherway
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> **********************************************************
>>> Electronic Mail is not secure, may not be read every day, and should not
>>> be used for urgent or sensitive issues
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> **********************************************************
>>> Electronic Mail is not secure, may not be read every day, and should not
>>> be used for urgent or sensitive issues
>>>
>>>
>>
>>
>
>



Reply via email to