Jun 02 2014

SharePoint 2013 User Profile “Put message” Error

Tag: CollaborationJulie Boudro @ 2:36 pm

Just recently, when configuring the User Profile Sync connection for SharePoint 2013 I ran into an issue after I select the organizational units. I received an “Unable to process PUT message” error. I reviewed the steps in the following post.

http://smallcitydesign.com/unable-to-process-put-message-when-configuring-synchronization-settings

However, the error still continued. Instead of deleting and recreating the entire User Profile Service application, I decided to delete the existing synchronization connection and recreate it. That seemed to do the trick! I was able to select my organization units and configure a full import.


Jun 02 2014

Windows Update Gotcha…

Tag: Access & Identity Management,Infrastructure,OtherErik Gilreath @ 7:02 am

I was working on patching our Windows servers recently and ran into a little hiccup. On several of the servers, after checking for updates, I received the following error message:

 EPG blog 1

 

 

 

 

It seemed a bit odd, so I decided to Bing it and see what I could find. I ended up being routed to the following Microsoft article: http://windows.microsoft.com/en-us/windows7/windows-update-error-0×80243004. The long and short of it is, that the Windows Update icon must be configured as Show icon and notifications for Windows Update to work.

 

EPG blog 2

 

 

 

Someone had changed it to Only show notifications, and that caused the error.

Hopefully this will save you a few minutes of frustration over a very simple little fix.


May 27 2014

Microsoft known issues for Project Online and Project Server 2013

Tag: Project ManagementDoug MacNEIL @ 7:27 am

Though Microsoft Project Server and Project Online are very well established products, they both have some known-issues.

Some are very specific:

  • OData Excel reports appear in English for Spanish and Japanese versions
  • Visual reports can only be viewed in English for this release

While others are wide reaching

  • Resource Plan ribbon disabled in Project Pro for Office 365
  • Pre-existing custom reports cannot be viewed in Project Pro for Office 365
  • User delegation does not work

However all are being reviewed by Microsoft for resolution. For review of Project Server 2013 known issues, please click here.


May 08 2014

PowerShell Automation To Create Operating System Query Based Collections in SCCM 2012 R2

Tag: InfrastructureC/D/H Consultant @ 8:04 am

After doing a number of System Center Configuration Manager Implementations, recreating the same query based operating system collections over and over gets pretty old. Being a bit of a PowerShell fanboy myself, I figured that there has to be an easier way to speed up this part of the deployment process. I love being right. Below are tested PowerShell scripts to automate the creation process for these OS query based collections in ConfigMan. The only thing you are required to change is specific to your 3 character SCCM Site Code in the line that starts with “Set-Location”. This site code is displayed in the title bar of the SCCM console. You can cut and paste sections at will, or just delete unnecessary collections after the script runs. I use ‘like’ rather than ‘equals’ on the naming convention for cases where “(Tablet Edition)” or “Advanced Server” is used in the OperatingSystemNameandVersion field. Limiting collections are in place for reduced computation and dynamic collection membership updates are used rather than scheduled updates. The folder structure in SCCM looks like:

  • Device Collections
    • Workstations
      • All Workstation Clients
      • Windows 2000
      • Windows XP
      • Windows Vista
      • Windows 7
      • Windows 8
      • Windows 8
    • Servers
      • All Server Clients
      • Windows Server 2000
      • Windows Server 2003
      • Windows Server 2008
      • Windows Server 2008 R2
      • Windows Server 2012 R2                               
 
#Import SCCM PowerShell Module
Import-Module (Join-Path $(Split-Path $env:SMS_ADMIN_UI_PATH) ConfigurationManager.psd1)
 
#Set ‘drive’ to SCCM Site Code
#CHANGE YYY TO YOUR SITE CODE
Set-Location YYY:\DeviceCollection
 
#Create “Workstations” Collection Folder
New-Item“Workstations”
 
#Create “All Workstation Clients” Collection
$NewCollection= New-CMDeviceCollection -Name “All Workstation Clients”-LimitingCollectionName “All Desktop and Server Clients”-RefreshType ConstantUpdate
Move-CMObject -InputObject $NewCollection -FolderPath .\Workstations
Add-CMDeviceCollectionQueryMembershipRule -CollectionName “All Workstation Clients”-RuleName “Workstation”-QueryExpression “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.OperatingSystemNameandVersion like ‘Microsoft Windows NT Workstation%’”
 
#Create “Windows 2000″ Collection
$NewCollection= New-CMDeviceCollection -Name “Windows 2000″-LimitingCollectionName “All Workstation Clients”-RefreshType ConstantUpdate
Move-CMObject -InputObject $NewCollection -FolderPath .\Workstations
Add-CMDeviceCollectionQueryMembershipRule -CollectionName “Windows 2000″-RuleName “Windows 2000″-QueryExpression “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.OperatingSystemNameandVersion like ‘Microsoft Windows NT Workstation 5.0%’”
 
#Create “Windows XP” Collection
$NewCollection= New-CMDeviceCollection -Name “Windows XP”-LimitingCollectionName “All Workstation Clients”-RefreshType ConstantUpdate
Move-CMObject -InputObject $NewCollection -FolderPath .\Workstations
Add-CMDeviceCollectionQueryMembershipRule -CollectionName “Windows XP”-RuleName “Windows XP”-QueryExpression “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.OperatingSystemNameandVersion like ‘Microsoft Windows NT Workstation 5.1%’”
 
#Create “Windows Vista” Collection
$NewCollection= New-CMDeviceCollection -Name “Windows Vista”-LimitingCollectionName “All Workstation Clients”-RefreshType ConstantUpdate
Move-CMObject -InputObject $NewCollection -FolderPath .\Workstations
Add-CMDeviceCollectionQueryMembershipRule -CollectionName “Windows Vista”-RuleName “Windows Vista”-QueryExpression “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.OperatingSystemNameandVersion like ‘Microsoft Windows NT Workstation 6.0%’”
 
#Create “Windows 7″ Collection
$NewCollection= New-CMDeviceCollection -Name “Windows 7″-LimitingCollectionName “All Workstation Clients”-RefreshType ConstantUpdate
Move-CMObject -InputObject $NewCollection -FolderPath .\Workstations
Add-CMDeviceCollectionQueryMembershipRule -CollectionName “Windows 7″-RuleName “Windows 7″-QueryExpression “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.OperatingSystemNameandVersion like ‘Microsoft Windows NT Workstation 6.1%’”
 
#Create “Windows 8″ Collection
$NewCollection= New-CMDeviceCollection -Name “Windows 8″-LimitingCollectionName “All Workstation Clients”-RefreshType ConstantUpdate
Move-CMObject -InputObject $NewCollection -FolderPath .\Workstations
Add-CMDeviceCollectionQueryMembershipRule -CollectionName “Windows 8″-RuleName “Windows 8″-QueryExpression “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.OperatingSystemNameandVersion like ‘Microsoft Windows NT Workstation 6.2%’”
 
#Create “Windows 8.1″ Collection
$NewCollection= New-CMDeviceCollection -Name “Windows 8.1″-LimitingCollectionName “All Workstation Clients”-RefreshType ConstantUpdate
Move-CMObject -InputObject $NewCollection -FolderPath .\Workstations
Add-CMDeviceCollectionQueryMembershipRule -CollectionName “Windows 8.1″-RuleName “Windows 8.1″-QueryExpression “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.OperatingSystemNameandVersion like ‘Microsoft Windows NT Workstation 6.3%’”
 
 
#Create “Servers” Collection Folder
New-Item“Servers”
 
#Create “All Server Clients” Collection
$NewCollection= New-CMDeviceCollection -Name “All Server Clients”-LimitingCollectionName “All Desktop and Server Clients”-RefreshType ConstantUpdate
Move-CMObject -InputObject $NewCollection -FolderPath .\Servers
Add-CMDeviceCollectionQueryMembershipRule -CollectionName “All Server Clients”-RuleName “Servers”-QueryExpression “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.OperatingSystemNameandVersion like ‘Microsoft Windows NT%Server%’”
 
#Create “Windows Server 2000″ Collection
$NewCollection= New-CMDeviceCollection -Name “Windows Server 2000″-LimitingCollectionName “All Server Clients”-RefreshType ConstantUpdate
Move-CMObject -InputObject $NewCollection -FolderPath .\Servers
Add-CMDeviceCollectionQueryMembershipRule -CollectionName “Windows Server 2000″-RuleName “Windows Server 2000″-QueryExpression “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.OperatingSystemNameandVersion like ‘Microsoft Windows NT%Server 5.0′”
 
#Create “Windows Server 2003″ Collection
$NewCollection= New-CMDeviceCollection -Name “Windows Server 2003″-LimitingCollectionName “All Server Clients”-RefreshType ConstantUpdate
Move-CMObject -InputObject $NewCollection -FolderPath .\Servers
Add-CMDeviceCollectionQueryMembershipRule -CollectionName “Windows Server 2003″-RuleName “Windows Server 2003″-QueryExpression “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.OperatingSystemNameandVersion like ‘Microsoft Windows NT%Server 5.2′”
 
#Create “Windows Server 2008″ Collection
$NewCollection= New-CMDeviceCollection -Name “Windows Server 2008″-LimitingCollectionName “All Server Clients”-RefreshType ConstantUpdate
Move-CMObject -InputObject $NewCollection -FolderPath .\Servers
Add-CMDeviceCollectionQueryMembershipRule -CollectionName “Windows Server 2008″-RuleName “Windows Server 2008″-QueryExpression “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.OperatingSystemNameandVersion like ‘Microsoft Windows NT%Server 6.0′”
 
#Create “Windows Server 2008 R2″ Collection
$NewCollection= New-CMDeviceCollection -Name “Windows Server 2008 R2″-LimitingCollectionName “All Server Clients”-RefreshType ConstantUpdate
Move-CMObject -InputObject $NewCollection -FolderPath .\Servers
Add-CMDeviceCollectionQueryMembershipRule -CollectionName “Windows Server 2008 R2″-RuleName “Windows Server 2008 R2″-QueryExpression “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.OperatingSystemNameandVersion like ‘Microsoft Windows NT%Server 6.1′”
 
#Create “Windows Server 2012″ Collection
$NewCollection= New-CMDeviceCollection -Name “Windows Server 2012″-LimitingCollectionName “All Server Clients”-RefreshType ConstantUpdate
Move-CMObject -InputObject $NewCollection -FolderPath .\Servers
Add-CMDeviceCollectionQueryMembershipRule -CollectionName “Windows Server 2012″-RuleName “Windows Server 2012″-QueryExpression “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.OperatingSystemNameandVersion like ‘Microsoft Windows NT%Server 6.2′”
 
#Create “Windows Server 2012 R2″ Collection
$NewCollection= New-CMDeviceCollection -Name “Windows Server 2012 R2″-LimitingCollectionName “All Server Clients”-RefreshType ConstantUpdate
Move-CMObject -InputObject $NewCollection -FolderPath .\Servers
Add-CMDeviceCollectionQueryMembershipRule -CollectionName “Windows Server 2012 R2″-RuleName “Windows Server 2012 R2″-QueryExpression “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.OperatingSystemNameandVersion like ‘Microsoft Windows NT%Server 6.3′”
 

May 05 2014

Latest Windows 8.1 Update adds new features

Tag: InfrastructureJulie Boudro @ 8:49 am

If you have installed the latest Windows 8.1 update, you may see a few new options when you first boot up your computer.

power  First is a new power button that appears on the site. This is a nice and quick way to power down your computer without having to log off first.
 Taks  The second is the pinning of apps in the task menu making them easier to close or swap between applications.
app As well as a new banner across the of apps to close or minimize the application.

Next Page »