hypercube33

I'll do a write up when I get a chance. I'd like to specify this for things like Java 32bit and 64bit and .Net. Funny how pre-reqs are sometimes the quirkiest things to install.

Thanks! I am hoping that they are accurate and that people can learn from my mistakes and things I've gathered from all over the internet trying to debug and answer questions I have faced! If there is any inaccuracies please let me know.

We do where I work -- our sales team. We are considering using the built-in always-on vpn that windows 7 provides.

C:\windows\ccm\logs\ContentTransferManager.log should shine a light on what is going on (or not) with any file transfers. Some digging into this lights that there may be a boundary problem, it may be a good place to double check. In my case when I hit this problem it was due to a 15GB package that is a monster (default cache is 5GB total!)

The old instructions for creating a package still apply, just make sure you specify the msi in the programs properties or else you'll have a bad time. I havent found a clean way of deploying it as an application -- yet. I will post a guide on this when I get a chance.

When I went to enable this feature, I noticed that it wasn't working out-of-the-box like I had expected. A little digging and I found that some external things need to be enabled for this to correctly work. Included in the guide are where the logs are (on the client) to check to see if this is working. Feel free to give any feedback! SCCM 2012 - Automatic User Device Affinity.pdf

I have created a guide that is a follow-up to the SCCM RC2 - Step 6: Software Updates Guide. Let me know what you think! SCCM 2012 - Automatically Updating Systems.pdf

I assume the correct way of making sure would be to filter deployment by doing: Deployment Types > Properties > Requirements to be for each and selecting the appropriate OS?

WIll do, hopefully I get some time to update this today!

A baffling thing happened to me that when we tried to give other IT co-workers access to remote control workstations for support roles, they were unable to search for a user and click on "view primary device" - a no-brainer to me. Here is my way of fixing this. This assumes you followed my guide on how to get user device affinity to automatically request approvals and have approved appropriate users to their devices. Link to this is here. First, we'll have to correct the security roles. Open Administration and navigate to Security Roles. From there, Right click and copy Remote Tools Operator and do a copy. Change the following Permissions: User Device Affinities: -Read: Yes Computer Association -Read: Yes Click OK and assign your remote support personnel to this security scope.

In this example, I am having trouble deploying the SCCM Console (for IT use -- remote view). It has a dependency of dotNet 4.0 which comes in 64bit and 32bit flavors. I'd prefer to install this automatically as needed, and install the correct version for each operating system. Before I dig into this deeper, is this the best way to accomplish this or should I seek to do this targeted for different collections or something else?

The memory requirements seem to help it in performance. SCCM collects quite a bit of data and is being very well utilized by the system. We have about 250~ clients and we are considering using more to boost speed.

I have attached the document on how to do this and posted a separate thread located here: http://www.windows-noob.com/forums/index.php?/topic/5957-automatic-user-and-device-affinity-guide/

Same - no success here. I did get our 2008 R2 Remote server's to show every single user to show as a primary and it showed up as a request in the affinity manager. However, all machines are not working other than these two in the Remote Desktop farm.

This is welcomed, and clears up any false perceptions I may have had. Thanks -- always the best source of information. Write some books already As for this: 4. I can also do a backwards, package install so FEP is available, ready to go before the user even logs into the machine by creating a package for FEP, and running as follows: scepinstall.exe /s /q as a package, and deploying in the task sequence not following your train of thought here. Whilst deploying Windows 7 via a task sequence, my supervisor wants the machine protected as soon as possible. Without running tests to see if it enables the Endpoint Protection during the "Install CM Client" task sequence or soon therafter: Would I want to manually deploy the EP2012 Client during a System Deployment Task Sequence to get the system protected before anything else occurs on our network?

So my situation is that I have clients install on every machine in our domain. I will be enabling the Endpoint Protection Role. From my tests, reading, and lab experiments the following will keep me from "accidentally" rolling FEP out to everyone. 1. Install EP Role on SCCM 2. Enable management but set install to FALSE in the default Policy 3. Setup a new policy to manage deployment for groups of users in a controlled way. 4. I can also do a backwards, package install so FEP is available, ready to go before the user even logs into the machine by creating a package for FEP, and running as follows: scepinstall.exe /s /q as a package, and deploying in the task sequence I'm 90% confident that nothing bad will happen, but I would love confidence increased before I fire away in production -Brian

I know you said you were making them, but I am doing it anyway and will have /my/ versions of the new RTM emailed to you, anyweb. Its up to him if he chooses to publish them or not. I have gotten a lot out of them, so I feel like I have to give back when I make them available to print for myself (in word files) that I should give back to the community.

Unfortunately, I am pressed for time. This made me blow the whole VM/SCCM server away and start over. Fortunately, this time it is working as expected and I am ahead of where I was a day ago. At least I am getting good at installing it, though I need to learn much more about troubleshooting it.

Dug around for the existence of PXE logs but cannot find any -- also didn't mention that WDS did not install any of the times I attempted to install SCCM. Not sure where logs would be for that, but I will look and upload them when I get a chance.

I did the following: 1. import the images and files from my SCCM 2012 RC2 server. All were manually imported (Copied the files, and added them manually) 2. set the boot images up but did not deploy them 3. added the pxe role to the server 4. deployed the pxe boot images 5. setup the OS installer for windows 7 6. set up the task list for windows 7 7. set up the image for windows 7 (captured using RC2) 8. set up a collection target 9 deployed the task sequence to the collection 10. added a VM with static mac to the collection 11. tried to pxe boot The VM is not getting DHCP on two subnets it should be getting -- in theory i should be getting another error than it timing out like its not on a network at all. VM is on a Hyper-V 2008 R2 Host. distmgr.log

I can upload them to somewhere i have converted a ton of them to word which is easy to save as PDF. I also corrected a few minor things like adding screenshots where one wasnt, etc.

I dont see how this product is anywhere near ready for production - how do we roll this out when the product is gold? It looks like its an all-or-nothing piece. I'd love to be able to test it on 10% of our machines to make sure it can uninstall current products with success and then kick it out - how would one do this?

Woops. Can this manage Windows CE Devices - we have 120 currently in use and I would at least like to see remote view on them.