BenjAdmin

Congratulatios Nial!

Why to target computers instead of users with sccm Managabilty disadvantages of targetting users: • When you target users for software deployments you will lose the manageability of your environment there you link the advertisement to the logon of the users onto a computer within the Active Directory domain. Those users can log on/off wherever they want and therefore software gets installed on computers where this software wasn’t supposed to be available. This also makes this software also available for other users who shouldn’t have access to that specific software package. • From time to time it is necessary that administrators or helpdesk operators take control of a users machine, this machine will be targeted for distribution of software intended for the Administrator / helpdesk operator. • There these users can log on to any desktop you will have no idea on where your software will get installed thus you don’t have any idea of how many software licenses for a specific product are used or how many times this software is unnecessarily installed. • Users will need to log off and log on again before the machine with the current user will be added to the correct collection to get its software advertised. When software is mandatory, a new logoff/logon is required to get it installed (due to the security token only being created at the time of log on to the machine). • When you target computers you will have less work there SCCM is primarily designed for this way of software distribution. This means less IT-costs and thus saving your company money in the long run. Technical disadvantages of targeting users: • There more software will get installed on the different clients in your environment because you can’t control these installations anymore; a larger overhead will be created on your network infrastructure. Some software packages are very large so this can have a real impact on the performance of the corporate network. • Although SCCM can target users and user groups; software distribution history on the local client is part of a different area in WMI and the right-click tools, SMSClient Center, and lots of other wonderful SCCM utilities either don't interface with that user-specific WMI area at all, or are inconsistent. Targeting users instead of computers will thus limit you in the use of your SCCM environment. Conclusion: Although targeting of users and user groups with SCCM is supported, it is strongly advised to NOT use this feature of SCCM! I edited my first post to include this summary

OK, found another reason thx to the link you gave me: Skissinger wrote there: "you know that although SMS can target users and usergroups, software distribution history on the local client goes into a different area in WMI, and the right-click tools, SMSClient Center, and lots of other wonderful SMS utilities either don't interface with that user-specific WMI area at all, or are inconsistent, so you want to advertise to the Machines, not the users." When I have created my reasoning, I will provide an overview here as well for future use. If someone has more suggestions, they are still welcome!

No one else has any suggestions?

As far as i know was the beta version limited in time. It is expired now and the final version is released, so i doubt it will be available for free anywhere.

Hi all, For a company migrating from Novell Zenworks to SCCM I have to motivate why they should target computers instead of users with softwarepackages. I allready have a few reasons, but i'd like to be as complete as can be, so I ask you guys for help. The points i have: You lose control of what is installed where, there you link advertisements to the logon on the computers. You lose control of the used licenses. If an administrator log's in on a client computer (to solve some problems for exemple), other software, not user proprietary gets installed. You create more overhead on the network there certain softwarepackages will be installed when not necessary what can be added to this list? Benefits of targetting users instead of computers are also welcome! kind regards, BenjAdmin Summary of this thread: Why to target computers instead of users with sccm Managabilty disadvantages of targetting users: • When you target users for software deployments you will lose the manageability of your environment there you link the advertisement to the logon of the users onto a computer within the Active Directory domain. Those users can log on/off wherever they want and therefore software gets installed on computers where this software wasn’t supposed to be available. This also makes this software available for other users who shouldn’t have access to that specific software package. • From time to time it is necessary that administrators or helpdesk operators take control of a users machine, this machine will be targeted for distribution of software intended for the Administrator / helpdesk operator. • There these users can log on to any desktop you will have no idea on where your software will get installed thus you don’t have any idea of how many software licenses for a specific product are used or how many times this software is unnecessarily installed. • Users will need to log off and log on again before the machine with the current user will be added to the correct collection to get its software advertised. When software is mandatory, a new logoff/logon is required to get it installed (due to the security token only being created at the time of log on to the machine). • When you target computers you will have less work there SCCM is primarily designed for this way of software distribution. This means less IT-costs and thus saving your company money in the long run. Technical disadvantages of targeting users: • There more software will get installed on the different clients in your environment because you can’t control these installations anymore; a larger overhead will be created on your network infrastructure. Some software packages are very large so this can have a real impact on the performance of the corporate network. • Although SCCM can target users and user groups; software distribution history on the local client is part of a different area in WMI and the right-click tools, SMSClient Center, and lots of other wonderful SCCM utilities either don't interface with that user-specific WMI area at all, or are inconsistent. Targeting users instead of computers will thus limit you in the use of your SCCM environment. Conclusion: Although targeting of users and user groups with SCCM is supported, it is strongly advised to NOT use this feature of SCCM!

Yes there exists an application that can do this. Link to the application But it doesn't hurt to google for something like this yourself next time, found it whitin 2 minutes...

Nice! I had the pleasure to meet him yesterday here in Belgium. Was a shorter presentation though

Ok, solved this issue myself. First i installed PHP on the first server Next I created a new service account Then I created a share on the secondary server containing the website's files. Added the service account and gave it readpermissions on the share. Created a virtual directory in IIS under the main site. Then used the new Serviceaccount on the primary IIS server to connect to the share Then I added the index.php to the standard documents Restarted the IIS service and now both sites are online under the same domain, using the same port (with a different subdirectory) but the files are both hosted on other servers. Greetings, BenjAdmin

Hi all, does someone know if it's possible to use the same public IP and Port 80 and dnsname and host content on 2 different IIS servers? To clarify my question here the situation: IIS 1: DNN server with a site and MS SQL database. IIS 2: PHP server with a site and MySQL database. Both servers should represent as one website to the external public, it shouldn't be vissible both parts are hosted on different servers. Als due to proxyservers and portrestrictions it's not able to reroute using different ports. Also the url for both servers should be the same. What on the other hand is possible is: www.xyz.com en www.xyz.com/site2 Is this possible and how should i do it? Thx in advance!

If this is the case: lock down the computer and publish your applications. restrict their rights and you won't have any problems when kids start to play because they can't any more

This post contains the links to all the important guides (to setup pxe, check the part of deploying Vista.) If you search a bit around on this site, I'm quite sure you can find the other how to's also. I'm sure Niall will be able to tell you were to look for those if they allready exist.

Google answers with this reply

Here you go: CCMSetup.exe CCMINSTALLDIR="C:\Temp" This command changes the location of the installation. So to answer your question is: Yes! More information: Technet Article

I guess a reboot is required there it involves changes to the registry key which cannot be mannually applied. Better count on it as being the case, I haven't needed this solution yet so I'm not completely sure to be honest. When tried, please let us know if the reboot ectually is required and don't forget to force the gp before trying and rebooting ;-) (To do this, type "gpudate /force" in a commandbox on an infected client computer to speed up things)

Updated previous post with the location of the adm-templates.

You can push an adm template changing the sitecodes through group policy. Use the Group Policy administrative template named ConfigMgr2007Assignment.adm supplied in the folder TOOLS\ConfigMgrADMTemplates on the Configuration Manager 2007 installation media to apply the site assignment configuration to client computers. Afther a reboot of the clients, those should point to the correct site. If you assign or reassign the client to a site using Windows Group Policy, the site code is stored in a registry key on client computers. To reassign a client to another site, change the Group Policy setting to update the registry key. Please take notice of the fact that you cannot change the registry key directly! More information on this subject can be found on the Technet site: Technet Article

If you are using DHCP snooping on the switches, please disable it and try again.

I almost finished a tutorial on how to do this. Will post this when ready, it's quite easy. (I expect it to be ready at the end of this week, beginning Next week)

Try this: @echo off cd x:\Windows\system32 bcdedit /set {default} device partition=c: bcdedit /set {default} osdevice partition=c: bcdedit /set {bootmgr} device partition=c: "echo" in front of a line means the "program" should write this line on the screen as text. It doesn't execute the line.

Hey Ricky, Have you updated the distribution points? I've seen similar behaviour before and everytime it came down to the distribution point not being updated.

You're welcome! I expected it. I'm glad it works now.

The one thing i remember about finding this site is that I was using google to solve a minor problem in my testenvironment. I'm using the site since... I'd like to take the opportunity to thank Anyweb and all contributors for the work put in this forum. It's an enormous asset to my daily work!