Sh500

Thanks. I saw similar posts in the forum describing what you have done. Not the ideal, but will have to do.

Thanks for the reply all. I thought as much. Yes, you definitely should be able to restrict individual areas. Especially considering this common area is shared between end user and potentially 'very destructive' functions.

Hi all, We have the need to lock down Windows 10 PCs. One of the things we are trying to restrict is 'Settings' (accessed from the Start Menu), BUT we would still want users to see and use 'Ease of Access'. Is this possible? Restricting selected 'control panel' items via GPO on Win7 and earlier was relatively straight forward, but cannot seem to figure it out on Win10. Thanks.

Hi all, I have just tried test installing Java 8 Update 51. I also currently have 7_67 installed on all machines (deployed via SCCM). I have used the following (SCCM 2012 r2): msiexec /i "jre1.8.0_25.msi" JU=0 JAVAUPDATE=0 AUTOUPDATECHECK=0 RebootYesNo=No WEB_JAVA=1 /q Have also selected the correct supersedence info to remove version 7_67. The install seems to run fine without any errors, including removal of 7_67 and installation of 8_51. The 'only' problem is that 'verifying java' fails and infers that there is no install of Java at all (!). I have already checked the usual things such as 'enable Java in browser', etc. I have re-checked verifying on a client with 7_67 and it 'passes' fine. Can someone suggest anything that could be wrong? EDIT: I was installing the 64 bit version for Java as the clients have a 64 bit OS and IE installed. Just tried with the 32 bit MSI and the install now works fine. Clients were running in 'non Enhanced Protected Mode"

Yep, I'm in the same boat. Although the Sage installs for me are only on the training lab PCs. It would be great if anyone does have info on applying the updates via SCCM. As mentioned elsewhere on the net, their tech support is very poor.

@free780 Can you explain how to do this please? I can see the default codes but not sure if they need to be modified or new ones added. I have just tried adding the extra 'suppress code' and changing the detection rule to a reg value. These still resulted in a 'software failure' message. On general note: Why is it that my .cmd script did not work and entering the code directly does? Is it something to with the script trying to run from a UNC path? I ask because, I tested a simple batch file that maps a network drive and that script also did not actually execute. It would just be good to know for future reference.

@Arthur, Entering the command directly does 'seem' to remove the software- but the client has a 'Removal Failed' as the status: As far as I can see from the client, it has removed all directories - and in this case the PDF Creator instance in 'Devices and Printers' too.

I am guessing I am missing out something fundamental in deploying a batch script via SCCM in general. Like I say, the 'uninstall.cmd' script that I have works fine when executed manually on the client PC.

I've tried both of them, as well as C:\Program Files (x86)

Yep, I have that boxed checked already.

Hi all, New to this forum and indeed SCCM. I have managed to setup a one site SCCM deployment. 'Application' deployments seem to be working fine and as expected. All clients will Windows 7 64 bit. I am still testing things at the moment. My latest application to be installed is PDF Creator. I have installed this via a 'manual scripted' method as an 'Application'. This seems to install fine on the test clients. As far as I am aware there is no official MSI for this program, so I thought I'd try to uninstall the software, via the following .cmd script: "C:\Program Files (x86)\PDFCreator\unins000.exe" /verysilent /SUPPRESSMSGBOXES /NORESTART This works fine when run manually but I cannot seem to get it working via SCCM. I have searched the net and there has been discussion about batch scripts and system rights, etc. Perhaps it's something to do with 'what folder the script needs to execute? Can someone please let me know, the full and proper procedure using SCCM 2012 to uninstall this program. Many thanks.