After downloading and installing, I first discovered the addon didn’t actually install. I needed it on both a Windows Server 2008 R2 box, and a Windows Server 2012 and they both had issues. On 2008, I discovered in the comments of the page I linked before, that the following fix was suggested:
someone gave a quick way to fix this in Powershell 3.0. Just run these commands in powershell and then test it out: Get-ChildItem “C:\Program Files\SCCMConsoleExtensions” | Unblock-File Get-ChildItem “C:\Program Files\SCCMConsoleExtensions\PSTools” | Unblock-File
Once you’ve got that, just run powershell, run the two commands and that seemed to be all I needed to do, the right click tools now worked perfectly.
On the Windows Server 2012 box though, the right click tools came up, but did nothing when any of the options were selected. It already has Powershell 3.0, but running those commands didn’t help. I then thought that re-trying the installer with the right click option ‘Run As Administrator’ would work, but no difference.
As per my “Windows 8 – Easy Admin Access” blogpost, I launched command prompt with those elevated privilidges and installed again. No luck! Finally, I then ran powershell.exe from the elevated command prompt, entered the two Unblock-File commands, and that did work. Keep in mind I even tried the above with the domain administrator account before running the elevated command prompt, so it really demonstrates how different security is in Windows 8 and Windows Server 2012.
Just because you’ve got God level access, and run something with ‘Run as Administrator” doesn’t necessarily mean you’ve got access!
Hi,
I’ve just completed upgrading my System Center 2012 environment to Service Pack 1, and seem to have run into a bug. Any existing Antimalware Policy (under Assets and Compliance > Endpoint Protection > Antimalware Policies) can’t be modified. When you try to modify them, you get an error saying “Unhandled exception has occured in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately. The SMS provider reported an error.”
There is then a large amount of unexciting details which I’ll put at the end of this post in case anyone searches for this issue. I can’t see anything of value in it, since it’s a “Generic failure”.
The best I can offer is a workaround. I couldn’t copy the existing policies as nothing happened when I tried. Newly created policies work fine, but rather than re-creating the existing ones, it will let you export each one to an XML file, then re-import it back in. Once that’s done, then just deploy the policy to the same collection as the old one, and finally delete the old broken policy. Hopefully you don’t have too many to do! If anyone comes up with a proper fix feel free to share.
As a side note, it looks like Microsoft missed removing the ‘Beta’ part of this setup message in the RTM version. It had me worried for a moment that I’d just installed the beta!
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException: The SMS Provider reported an error. ---> System.Management.ManagementException: Generic failure at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode) at System.Management.ManagementObject.Put(PutOptions options) at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport) --- End of inner exception stack trace --- at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport) at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put() at Microsoft.ConfigurationManagement.AdminConsole.ClientAgentSettings.HomePageControl.SaveCustomizedSettingObject(List`1 settingObjects) at Microsoft.ConfigurationManagement.AdminConsole.ClientAgentSettings.HomePageControl.ApplyChanges(Control& errorControl, Boolean& showError) at Microsoft.ConfigurationManagement.AdminConsole.SmsPageControl.OnApplyChanges() at Microsoft.ConfigurationManagement.AdminConsole.SccmPageControlDialog.Put() at Microsoft.ConfigurationManagement.AdminConsole.SccmPageControlDialog.OnOk() at Microsoft.ConfigurationManagement.AdminConsole.SccmPageControlDialog.buttonOK_Click(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** JIT Debugging **************To enable just-in-time (JIT) debugging, the .config file for thisapplication or computer (machine.config) must have thejitDebugging value set in the system.windows.forms section.The application must also be compiled with debuggingenabled.
When JIT debugging is enabled, any unhandled exceptionwill be sent to the JIT debugger registered on the computerrather than be handled by this dialog box.
It’s just specifying the variable OSDComputerName needs to be set for your Unknown Computers collection, which will work as long as you have your OSD task sequence advertised there too.
The second thing, which was more of an issue, was that my PC wasn’t detecting my PXE server after the first time, even though the OSD Task Sequence bombed out.
In SCCM 2007 it didn’t quite work this way, generally if it bombed out there would be no record and you could continually PXE boot as many times as you liked. In 2012, as soon as you get to the list of available task sequences, the ‘Unknown Computer’ record is created.
Hi,
I’ve just been troubleshooting a PC that was failing when the SCCM 2012 client was being pushed to it, with the below error located on the client’s log file ccmsetup.log:
MSI: Setup failed due to unexpected circumstances
The error code is 80041026
After trying the install locally and still having it fail, I took the next logical step and googled it.
I found this blog, which had a similar issue but different error code:
net stop winmgmt Using Windows Explorer, rename the folder %windir%\System32\Wbem\Repository. (For example, %windir%\System32\Wbem\Repository_bad). %windir% represents the path to the Windows directory, which is typically C:\Windows.
net start winmgmt
rundll32 wbemupgd, UpgradeRepository
That was it, no reboot required. Retrying the install again was then successful.
These instructions will let you run Remote Control from System Center Configuration Manager 2012 without needing any extra software installed. The logged on account still needs ‘Remote Tools Operator’ access from inside SCCM 2012, but they can fire this up to remotely connect after this.
Keep in mind that if you have a 64 bit OS, the path for the files will be “Program Files (x86)”. Also, this works on both 32 and 64 bit OSs, while the old 2007 required separate copies.
It should be a nice easy way to remove VNC or other less secure connection methods internally from your company.
I’ll also add that the 2012 version seems much more reliable than the 2007, especially with visual issues.
