Search the Community

Hello, I`m trying to recreate my customsettings.ini file in order to Join and provide a computer name during OSD, i`m wondering if it`s possible to achieve it based on the "constraints" that we have : 1-Diffrent OUs for each type of computer and locations: Desktop and Laptop 2-Diffrent defaultgateway for floor in each location. 3-Diffrent naming convention for each location and diffrent computer type. Thanks,

I currently have multiple customsettings.ini files that assign computer names based on location + asset tag. I'm wondering if there is a way to have only one file that can do the same when selecting the location from a front end HTA. PS: I can't use the default gateway as the computers are imaged from the same location. Thanks,

Hello Folks, Long time Windows Noob fan, first time poster... I have a question about a Task Sequence in SCCM with MDT... So when creating a TS via MDT, you'll have that nice wizard that helps you out and I could not find anything that would define when to create a new XYZ Package and when to reuse it or not reuse it in another SCCM MDT Task Sequence... Create MDT Task Sequence > Boot Image Step > you have a choice to use an existing one or create a new one... Since I only have the stock SCCM Boot images, i do want to make an MDT boot image for x86 and x64... - Can I use these MDT Boot Images for another TS, if yes, when would i want to create another set of MDT Boot Images x86 and x64? Create MDT Task Sequence > MDT Package Step > you have a choice to use an existing or create a new one. When you create a new one, the folders at the given UNC Path look like as if it is a new deployment share which you would use for WorkBench. - Can I use this MDT Package for another TS, if yes, when would i want to create another set of MDT Packages? Also, what is the best practices for naming convention or organization? Create MDT Task Sequence > CustomSettings.ini Step > again, you have a choice to use an existing or create a new one. Since i dont have one, i'd create a new one but when would you want to reuse it and when would you want to create a brand new one? For all 3, i feel like if i make a new anything, i should make a new folder though i'm not quite sure what the best folder plan is for organization would be. Thank you for any help, i really do appreciate it!

Hi there Hopefully someone can help me out here. I plan on using a custom UDI Task Sequence to deploy a particular software package in our organization. The reason why a Task Sequence is been used is that we want to able to allow local admins/users choose the language of the software package that gets installed. I actually have it working already where, depending what a user chooses in the UDI, triggers a Task Sequence variable to run and install the particular language that the user had chosen. This works just fine and will probably suffice for our needs but i was hoping to add some more logic into the TS so that it would detect the OS language that the user has and then have the equivalent language of the software package already selected when they reached the the selection screen. As an example, if a user happened to have a Japanese OS, then when they came to the selection screen for the software package, the Japanese version would be automatically selected. I have already done something similar in the past with an OSD scenario (using CustomSettings.ini) where the default gateway IP determines what the timezone, keyboard settings, etc are automatically selected but what i'm trying to attempt right now is a "refresh" scenario, i.e., the TS will run inside the Windows OS and not PE. Anyone have any ideas on this? Thank you.