Search This Blog

Monday, December 30, 2013

SSRS - User does not have required permissions

You might see this error when trying to configure SQL Reporting Services after installation.

User does not have required permissions. Verify that sufficient permissions have been granted and Windows User Account Control (UAC) restrictions have been addressed.

image

The problem is that UAC is active.

image

We do not want to disable User Account Control, so instead start Internet Explorer as administrator.

image

And then we are able to do the configuration.

image

Thursday, December 26, 2013

Install Printer driver

Some times I need to install a printer driver silently, this could for example be in a SCCM Task Sequence.

One way around this is to use the build-in tools in C:\Windows\System32\Printing_Admin_Scripts

Lets try to install the HP Universal Printer Driver this way, by using the command:

cscript "C:\Windows\System32\Printing_Admin_Scripts\en-US\prndrvr.vbs" -a -m "HP Universal Printing PCL 6 (v5.7.0)" -i "C:\drv\hpcu155u.inf"

image

After this the driver is installed as shown in the Print Server Properties.

image

See more information regarding prndrvr.vbs here http://technet.microsoft.com/en-us/library/cc754632.aspx

We can use another script, prnmngr.vbs to install a printer.

With this command we install a printer called temp pointing to LPT1 and using the driver we just installed:

cscript "C:\Windows\System32\Printing_Admin_Scripts\en-US\prnmngr.vbs" -a -p "temp" -m "HP Universal Printing PCL 6 (v5.7.0)" -r "lpt1:"

image

The printer is installed as shown in Devices and Printers:

image

Se more information regarding prnmngr.vbs herehttp://technet.microsoft.com/en-us/library/cc725868.aspx

Installing the printer will also generate the “famous”  BUD file that sometimes is cursing printing problems. As an example problems with the BUD file can lead to very slow printer dialog boxes.

The .BUD file is a binary printer description file that is used to increase spooler efficiency for printer drivers.

Now lets delete the printer again with the command:

cscript "C:\Windows\System32\Printing_Admin_Scripts\en-US\prnmngr.vbs" -d -p "temp"

image

And finally we delete the Printer driver with the command:

cscript "C:\Windows\System32\Printing_Admin_Scripts\en-US\prndrvr.vbs" -d -m "HP Universal Printing PCL 6 (v5.7.0)" -e "Windows x64" -v 3

image

This is just examples on how to use some of the printing tools, there are lots of possibilities and even more tools, so take a closer look at the tools when your need to automate printers.

image

Monday, December 16, 2013

Change network type from public to private

You might want to change your network type from public to private in Windows 8.1, in these examples I have used Windows 8.1 Enterprise version.

Lets first check the current type, right click the network icon in the notification area:

image

Select open Network and Sharing Center:

image

The current type is Public network:

image

Now open File Explorer and click on Network:

image

You will se a message in the top saying that Network discovery and file sharing are turned off, network computers and devices are not visible. Click to change, click on the message and select Turn on network discovery and file sharing:

image

In the next popup select No, make the network that I am connected to a private network:

image

The network now has the type Private:

image

By selecting Change advanced sharing setting you will be able to disable network discovery again without changing the type of the network, if desired.

image

The explained way will also work for Windows 8.

Monday, December 9, 2013

Windows 8.1 Boot to Desktop GPO

In Windows 8.1 we have an option to boot windows directly to the desktop (desktop mode).

Right click on the taskbar and select Properties.

image

Select the Navigation tab and under Start screen, check the first option that says When I sign in or close all apps on a screen, go to the desktop instead of Start.

image

And of course it’s possible to set this in a GPO, go to User Configuration – Policies – Administrative templates – Start Menu and taskbar – Go to the desktop instead of Start when signing in or when all the apps on a screen are closed

  image

And enable the policy.

image

Configuration Manager Toolkit for System center 2012 R2

Microsoft has now released the Configuration Manager Toolkit for System center 2012 R2, one I have been looking forward to.

 

The Microsoft System Center 2012 R2 Configuration Manager Toolkit contains fifteen downloadable tools to help you manage and troubleshoot Microsoft System Center 2012 R2 Configuration Manager.

http://www.microsoft.com/en-us/download/details.aspx?id=36213

 

image

 

From the download link:

The following list provides specific information about each tool in the toolkit.

Note: Items with an * are new in the R2 Toolkit and require Microsoft System Center 2012 R2 Configuration Manager for full functionality.

Server Based Tools

  • * DP Job Manager - A tool that helps troubleshoot and manage ongoing content distribution jobs to Configuration Manager distribution points.
  • * Collection Evaluation Viewer - A tool that assists in troubleshooting collection evaluation related issues by viewing collection evaluation details.
  • * Content Library Explorer - A tool that assists in troubleshooting issues with and viewing the contents of the content library.
  • Security Configuration Wizard Template for Microsoft System Center 2012 R2 Configuration Manager - The Security Configuration Wizard (SCW) is an attack-surface reduction tool for the Microsoft Windows Server 2008 R2 operating system. Security Configuration Wizard determines the minimum functionality required for a server's role or roles, and disables functionality that is not required.
  • Content Library Transfer – A tool that transfers content from one disk drive to another.
  • Content Ownership Tool – A tool that changes ownership of orphaned packages (packages without an owner site server).
  • Role-based Administration Modeling and Auditing Tool – This tool helps administrators to model and audit RBA configurations.
  • Run Metering Summarization Tool - The purpose of this tool is to run the metering summarization task to analyze raw metering data


Client Based Tools

  • Client Spy - A tool that helps you troubleshoot issues related to software distribution, inventory, and software metering on System Center 2012 Configuration Manager clients.
  • Configuration Manager Trace Log Viewer – A tool used to view log files created by Configuration Manager components and agents.
  • Deployment Monitoring Tool - The Deployment Monitoring Tool is a graphical user interface designed help troubleshoot Applications, Updates, and Baseline deployments on System Center 2012 Configuration Manager clients.
  • Policy Spy - A policy viewer that helps you review and troubleshoot the policy system on System Center 2012 Configuration Manager clients.
  • Power Viewer Tool – A tool to view the status of power management feature on System Center 2012 Configuration Manager clients.
  • Send Schedule Tool - A tool used to trigger a schedule on a client or trigger the evaluation of a specified DCM Baseline. You can trigger a schedule either locally or remotely.
  • Wakeup Spy – A tool that provides a view of the power state of Configuration Manager client computers and which operate as managers or manages.
Supported Operating System

Windows 7, Windows 8, Windows Server 2008 R2, Windows Server 2012

Friday, December 6, 2013

System Center Endpoint Protection Client Update

Update 05-03-2015

http://larslohmann.blogspot.dk/2015/03/system-center-endpoint-protection.html

Original Post:

Microsoft has released an update for the System Center Endpoint protection clients.

This updates is available for SCCM 2012 R2 Endpoint Protection Clients, SCCM 2012 SP1 Endpoint Protection Clients and Forefront Endpoint Protection 2010 Clients.

KB2907566

image

The update includes this file:

image

The installation is pretty straight forward, here without the need for a package to update more site servers.

image

image

image

image

image

image

image

To update the existing clients you can use Automatic Client Upgrade found under Site Configuration – Sites - Hierarchy Settings

image

image

Beware of potential problems with Maintenance Window and that the update is initiated by a scheduled task:

image

Link to more information

After updating the client will report version 4.4.304.0

image

Monday, December 2, 2013

The Group policy Client service failed the sign-in

I have seen this error first time you try to login on a newly SCCM 2012 R2 deployed Windows 8.1 computer.

The Group policy Client service failed the sign-in.

The universal unique identifier (UUID) type is not supported.

image

This is only happening when I use the original RTM ISO en_windows_8_1_enterprise_x64_dvd_2791088.iso (without any software update), if I instead use the latest en_windows_8_1_enterprise_x64_dvd_2971902.iso the error is gone.

Apparently this ISO is updated with the Windows 8.1 and Windows Server 2012 R2 General Availability Update Rollup

image

 

Update 26-06-2014

Microsoft has now a documented workaround http://support.microsoft.com/kb/2976660/en-us if you still are are expiring the problem.

image

Thursday, November 28, 2013

Disable Help Sticker notifications in Windows 8.1 GPO

Windows 8.1 introduces Help Stickers so we can learn how to work with the new features that the OS has to offer. The feature is great and can help you learn the new features quickly if you like the popups.

These help stickers are easy to recognize by their black/brown, red/orange and white colors.

If you would like to disable this feature in a Enterprise environment Microsoft has provided a GPO for this.

imageimage

In order to disable the popup in a GPO use

Computer Configuration – Policies –Administrative Templates – Windows Components – Edge UI – Disable help tips

image

Enabling this policy will disable the help sticker popup.

image

This policy is also available in user context.

image

Monday, November 25, 2013

Unknown Computers and Required Task Sequence that fails – Part 2

last time I took a look at the Unknown computer object created when a task sequence fail http://larslohmann.blogspot.com/2013/11/unknown-computers-and-required-task.html.

But in some situations this object is not created, let try to remove the network while WINPE is downloading:

image_thumb17

It will off course fail and if you try to PXE boot again we are back to No boot filename received :

image

Again the PXE log will show:

no advertisements found

No boot action.

Rejected.Not serviced.

This time we are unable to use Clear Required PXE Deployment because the computer is simply not shown in the GUI.

If we take a closer look at the table LastPXEAdvertisment, we will find the MAC address in the table.

image

So how are we going to be able to PXE boot this computer again?

One way could be to import a computer into SCCM with the MAC address, Clear the PXE of this machine and delete the computer again, this way it will be back to unknown without any previous PXE boot.

Another way is to delete the entry in the table Smile

Maybe there is something that I have overlooked, but should this really be a problem?

Please let me know if some of you got a better solution.

Monday, November 18, 2013

Unknown Computers and Required Task Sequence that fails – Part 1

When deploying a Required Task Sequence to unknown Computers in SCCM 2012, you might be unable to PXE boot the computer again if the installation fails for some reason. So lets take a closer look at the documentation:

If the computer fails to install the operating system image or the Configuration Manager client, an “Unknown” record for the computer is created and the computer appears in the All Systems collection.

If you try to PXE boot the Computer again you will get the error No boot filename received

image

This is because the computer is no longer unknown, probably not in the target deployment collection, and we also need to Clear Required PXE Deployment to be able to PXE boot the device again.

In the PXE log we will see information like:

no advertisements found

No boot action.

Rejected. Not serviced.

image

An Unknown computer object has been created in All Systems.

image

We can grab this type of computers with a query, this will make it possible to target them with the deployment and to clear the required PXE Deployment.

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.Unknown = 1

image

image

image

And here we go again:

image

I must say that I am not very keen on required task sequences but sometimes they are needed, stay tuned for Part 2  Smile