mickblanko

Off the top of my head I would think in 2012 we could do something along the lines of… Create a new application with the new Firefox version Set the new Firefox version to ‘supersede’ the old Firefox version Remove the old Firefox deployment and retire the old Application Deploy the new Firefox version to the required collection Can anyone suggest a better way? Of course you could do it via SCUP and SCCM Software updates if you have some cash: http://social.technet.microsoft.com/Forums/en-US/configmgrsum/thread/dc973dde-7886-4a06-bb51-67fb05238ed6

It’s very similar to SCCM 2007 from what I’ve seen. I haven't even noticed the differences. You can either go to the properties of the boot image and add the driver/s in there or (probably a better way) select the desired driver/s from ‘drivers’ sections of the software library and right click the driver, select ‘Edit’ then ‘Boot Images’, and inject the drivers into the desired image that way. I tend to do it the second way as I can sort the drivers by the categories I have already defined (eg “WinPE x86 drivers”) which makes them easier to select

I am running RC 2 and I have the same question/issue. I can’t find a way to revoke approves once they have been granted. One example (other than a fat fingered IT person clicking the wrong button and granting approval by accident) would be a finance person requesting access to a restricted finance app, this gets approved and works well until the user takes a new position somewhere else in the organization eg as a PA. Now the approval for the finance app can’t be removed and the user can pull this app down to any computer they wish. Not ideal. Anyone worked out a solution to this?

Ok never mind, I think I've worked it out. I changed a few things and it seems to have been a firewall issue (possibly in conjunction with some other issues - I'm not 100% sure). Anyway if you see this error in future, check your firewall

On closer inspection of the mcsprv.log file I've noticed the following warning: "Could not load logging configuration for component mcsprv. Using default values." Can someone with a working multicast setup check their logs to see if this warning is normal and thus can be safely be ignored?

my understanding is that the boot image has to come from the PXE server (specifically the smspxeimages$ share) when you are doing a PXE boot. you can push your boot images to other distribution points, but they will only be used when an OSD task is initiated from within Windows not when PXE booting.

i made a similar mistake when first trying to setup PXE boot. i configured WDS after installing it and that seemed to cause alot of issues. i blew away the VM and tried again, but this time i let SCCM configure WDS. that how i've done it ever since and my PXE setups have never caused an issue since then. good luck

Just to clarify, copy and paste will work via RDP by not via Remote Assistance. Its a limitation/feature of remote assistance that it doesn't share the clipboard. It drives my service desk nuts too.

Hi guys, First of all thanks for all the fantastic guides and information on this site. It’s saved me countless hours and grey hairs. I've got a bit of a problem with regards to multicasting and I’m hoping someone out there might have come across this issue before and know the solution. I've followed all the guides and setup a 2008 R2 server and configured it as a DP and a multicast service point. The ‘site status / component status’ looks fine and so do the logs on the multicast server, but when I try to send out anything via multicast (eg winpe or an OS Image) it fails to start the multicast session and the smsts.log shows the following error: ….. Performing multicast download from mcs://server.com/SMS_MCS/.sms_mcs?filePath=\\server.com\SMSPKGE$\HSX00002\&PackageFlags=202375168&packageID=HSX00002&version=21. encryption required:false “Unable to find the multicast dll“ …. I've setup a completely separate DEV environment and it has the exact same issue, so I’m assuming that it’s probably something that I’m doing wrong somewhere. I've searched the servers and there is no file called multicast.dll. Does anyone have any ideas? Kind regards, Michael