For VNC creating VNC Shortcut

Powershell script For VNC creating VNC Shortcut

$a = Get-WmiObject -query "select * from Win32_NetworkAdapterConfiguration where IPEnabled = $true" |

  Select-Object -Expand IPAddress | 

  Where-Object { ([Net.IPAddress]$_).AddressFamily -eq "InterNetwork" }

# Create a Shortcut with Windows PowerShell

$TargetFile = "c:\support\vncviewer.exe"

$ShortcutFile = "x:\windows\temp\VNC.lnk"

$WScriptShell = New-Object -ComObject WScript.Shell

$Shortcut = $WScriptShell.CreateShortcut($ShortcutFile)

#$c = $targetfile + $a

$shortcut.TargetPath = $TargetFile

$Shortcut.Arguments = "$a /password 1234"

$Shortcut.Save()

Windows Update for Business not WSUS

WufB:  Windows Update for Business:

Windows Update for Business enables information technology administrators to keep the Windows 10-based devices in their organization always up to date with the latest security defenses and Windows features by directly connecting these systems to Microsoft's Windows Update service. By using Group Policy Objects, Windows Update for Business is an easily established and implemented system which enables organizations and administrators to exercise control on how their Windows 10-based devices are updated, by allowing:

• Deployment and validation groups; where administrators can specify which devices go first in an update wave, and which devices will come later (to ensure any quality bars are met).
• Peer-to-peer delivery, which administrators can enable to make delivery of updates to branch offices and remote sites with limited bandwidth very efficient.
• Use with existing tools such as System Center Configuration Manager and theEnterprise Mobility Suite.

Supported Devices:

All devices running Windows 10 Pro, Enterprise, and Education on the Current Branch for Business (CBB) are Windows Update for Business eligible.

 

For Windows 10 updates has been recently released on November 12 and with that recent update, have introduced a new GPO settings call "Defer Upgrades and Updates".

To see what that setting looks like, open "Local Group Policy Editor" (Run –>gpedit.msc) and browse to "Computer Configuration" –> "Administrative Templates" –> "Windows Components" –> "Windows Update" and you will find the below screen.

The new "Defer Upgrades and Updates" introduces 3 new options:

1. Defer upgrades up to 8 months (1 month increment)
2. Defer updates up to 4 weeks (1 week increment)
3. Pause Upgrades and Updates until the next update/upgrade release (around 30 days)

Note 1: You can't use those settings in conjunction with WSUS. if you specify an internal update service location, above settings will be ignored.

Note 2: By just enabling this GPO setting and not delaying anything (leaving both durations to 0), it will turn the target computers to CBB (Like the old GPO setting "Defer Upgrade" was doing in the Windows 10 RTM build).

 

Get IP address Powershell Script

Below are the script for getting Ipaddress with Powershell

Method 1:

Get-WmiObject -query "select * from Win32_NetworkAdapterConfiguration where IPEnabled = $true" | %{$_.IPaddress -notmatch 'fe80'}


Method 2:

$a = Get-WmiObject -query "select * from Win32_NetworkAdapterConfiguration where IPEnabled = $true" |
  Select-Object -Expand IPAddress |
  Where-Object { ([Net.IPAddress]$_).AddressFamily -eq "InterNetwork" }


When i Call $a I get Ipaddress results...

SSD Machines failed with BSOD

This can be fixed by installing KB 2990941 and then  kb 3087873

Update to add native driver support in NVM Express in Windows 7 and Windows Server 2008 R2

BSOD error 0x0000007E

STOP: 0x0000007E (parameter1, parameter2, parameter3, parameter4)

https://support.microsoft.com/en-us/kb/2990941

https://support.microsoft.com/en-us/kb/3087873

If you Get <![LOG[Setting wizard error: There are no task sequences available for this computer.] as in your SMSTS/log file then check these points...

Ø  The computer is not imported in the console if you are using known computers not unknown computers

Ø  If you are using unknown computers, delete any devices with the name unknown (but whatever you do DO NOT delete the two builtin unknown records)

Ø  Make sure that the TS is enabled

Ø  Make sure the device is in a collection with a TS deployed to it

Ø  Change the schedule of the deployment to yesterday

Ø  Check if the TS deployment is set to ‘configmgr client, media and PXE’

Ø  The computer is imported with a mac address that is already in the database (check the report ‘MAC computers for a specific mac address’

Ø  The computer still has a cached pxe advertisement

Ø  The computer is in the console but is not approved

Ø  The computer has incorrect date/time settings

Ø  Check if the DP certificates have not expired

Ø  The Boot Image associated to the TS has not been distributed yet

Ø  The ResourceId of the computer that boot’s is already used by another machine in the console (verify the ‘itemkey’ value from SMSPXE.log versus the result from select * from v_R_system where resourceid=’….’

Ø  The biosguid of the computer that boot’s is already used by another machine in the console (check the biosguid from SMSPXE.LOG versus the result from select * from v_R_system where smbios_guid0 LIKE ‘%…%’ (try with a part of the biosguid…)

Ø  Delete the device from the console and import it again

Ø  Check if there are any bad policy assignments in the sql db:

Ø  SELECT * FROM ResPolicyMap WHERE machineid = 0 and PADBID IN (SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL) if this returns anything then you have to delete the items with: Delete FROM ResPolicyMap WHERE machineid = 0 and PADBID IN (SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL)

SCCM / Configuration Manager Current Branch vs SCCM 2016

In December 2015 MS introduced Current Branch (CB) method for SCCM too., like we have for Windows 10.

What it means to me ? 

MS can deliver SCCM  moving from longer release cycles to regular updates designed to support the faster way of updates for Windows 10 and Microsoft Intune and align with these products & features updates support as it is Business support application tool. 

There is no Current Branch for Business (SCCM CBB)  for SCCM, it's only SCCM Current Branch. 

SCCM CB has Technical previews where it automatically appears in SCCM Console. 

You can use these technical previews, however you can't degrade one version number to other. Typically, new versions of the technical preview are available each month  In the admin console, new versions appear as “Configuration Manager Technical Preview YYMM.” 

All these Feedback & new features will be bundled with upcoming SCCM 2016 version, So do not think that there is no 2016.... it will be release soon......

Are we talking similar to Microsoft update ? Even though I do not use Windows 10 in my infra I must have to update? 

Yes, if you have SCCM CB, and it must go for regular updates regardless of you support it's supported products in your infra. 

Each version is supported to 12 months. Each incremental update version may fix some security updated and include some new features, Where as SCCM 2012 / R2 (not Current Branch) versions will get only CU's to fix the security or bug fixes ( So ideally the CB update versions and CU's are same however CB are more frequent with some excited new features other wise both are same).  Similarly windows 10 CB / CBB / LTSB will be supported if you update SCCM CB to N+1 and applications compatibility to N-1. 

Tip of the Day................>
selfhost testing : The first recipients of builds are Microsoft employees who begin what Microsoft calls selfhost testing

SCCM / Configuration Manager Current Branch vs SCCM 2016

In December 2015 MS introduced Current Branch (CB) method for SCCM too., like we have for Windows 10.

What it means to me ? 

MS can deliver SCCM  moving from longer release cycles to regular updates designed to support the faster way of updates for Windows 10 and Microsoft Intune and align with these products & features updates support as it is Business support application tool. 

There is no Current Branch for Business (SCCM CBB)  for SCCM, it's only SCCM Current Branch. 

SCCM CB has Technical previews where it automatically appears in SCCM Console. 

You can use these technical previews, however you can't degrade one version number to other. Typically, new versions of the technical preview are available each month  In the admin console, new versions appear as “Configuration Manager Technical Preview YYMM.” 

All these Feedback & new features will be bundled with upcoming SCCM 2016 version, So do not think that there is no 2016.... it will be release soon......

Are we talking similar to Microsoft update ? Even though I do not use Windows 10 in my infra I must have to update? 

Yes, if you have SCCM CB, and it must go for regular updates regardless of you support it's supported products in your infra. 

Each version is supported to 12 months. Each incremental update version may fix some security updated and include some new features, Where as SCCM 2012 / R2 (not Current Branch) versions will get only CU's to fix the security or bug fixes ( So ideally the CB update versions and CU's are same however CB are more frequent with some excited new features other wise both are same).  Similarly windows 10 CB / CBB / LTSB will be supported if you update SCCM CB to N+1 and applications compatibility to N-1. 

Quote of the Day................>
selfhost testing : The first recipients of builds are Microsoft employees who begin what Microsoft calls selfhost testing