HSChronic

Ah thanks. Now that leaves me with finding a way to use custom names since with standard names I can just use customsettings.ini

I went to modify my unknown systems collection today to add the OSDComputername variable to it and the ability to add new variables is greyed out. I am the only user on this configmgr server and I am a full admin so it isn't a permissions issue unless it is something with out of the box permissions. ConfigMGR 2012 SP1 beta running on: Server 2012 RTM SQL Server 2012 CU2 (remote) the server is working fine, just this one odd thing I noticed.

AdminStudio 11 is the best for this. I don't think Wise is even making package studio anymore. The process sometimes is very straight forward and it is just a matter of building a VM, installing your conversion studio, then monitoring the install. Other times it is a lot more involved and requires going into the package framework after it is built and modifying things.

How advanced do you want your task sequences? For instance my Task Sequences are very WMI query heavy, this way I can cut down on a task sequence for every different type of configuration or machine out there (I'm not talking apps, more like 32-bit Windows XP, 32-bit Windows 7, workgroup machine, domain machine). I have 4 task sequences in my environment and I am always trying to find a way to make them more simple and easier for people out there. If I could get down to 1 task sequence that asks for 1 or 2 variables then images the machine from there that is truly the magic of MDT ZeroTouch deployments. I have not messed much with UDI though, so I can't speak to the benefits of that.

If you create a MDT task sequence it will recreate this for you. It is basically nothing more than a package pointing to the client install files on your server and then using CCMSetup.exe with the parameters you specify in the OSD TS, or program.

SSRS is not working for me in my instance.

not in the console, from what I remember when I asked this on connect was there would be a way to either leverage the SDK or WMI on the machine to set these.

It just ran fine on my site. I have no special power management schemes assigned other than high performance and power saving.

Can you take a screen shot of your Task Sequence and post it here? Also check the reports to see if the client uploaded the failure to the management point.

It will be in X:\Windows\Temp before you partition and deploy an OS to a computer. Make sure you have command prompt enabled on your boot image.

Just installed this on my 2012 Site. I am impressed with it. I used SEP with Altiris a little while back and liked that. Though SEP has gone downhill in the past few years. SEP doesn't catch any of the real nasty malware out there like the fake anti-virus ones. I can't wait to play with FEP a little more and see how that stacks up compared to Eset Smart Security which is what I was using.

Give me a little time I can do this for you. I did this back with beta 1 and it worked great.

This usually happens like the error says when something in the database is moved or deleted and the console isn't refreshed. If you haven't changed anything with your site I would go to the ConfigMGR 2012 beta 2 connect site and report this as a bug. The folks at MS might be better suited to help track down this bug/error.

What does the SMSTS log say? You said you created a package from the MSI? So that would give you the per-system unattended and whatnot correct? You shouldn't create the package using that because the commands for installing a client in a TS are't going to work if you created the package by importing the MSI. Create a package from definition is correct but you want to use the built in definition for the Client not one created from importing the MSI.

I have set up Native Mode for SCCM 2007 multiple times with no issues. However for the life of me I can't get Clients to communicate over HTTPS to the MP. I know with 2012 I don't need a site signing cert anymore, so that is one headache out of the way. I have my MP set to use HTTPS and the server certificate that was issued by my CA through group policy. Clients use their certificates issued the same way. Everything seems fine, but I can't get the clients to pull policy. I get the following error "Authority xxx does not have an associated policy agent configuration". The bindings on the MP are set correctly. The only thing that I can think of is that since SSRS is on the same server that might be conflicting with it some how. Any ideas where to go or what logs to check? I don't see any errors in the component config, and I don't see anything in the logs that point to a PKI failure.