Download large file from google drive

If there is the large file from google drive and you don't want download from browser, you may try this :

So for example when you share a file on google drive publicly the sharelink looks like this:

https://drive.google.com/file/d/XXXXXXXXXXXXXXX/view?usp=sharing

Then you copy the file id and create a googledrive.com linke that look like this:

https://www.googledrive.com/host/XXXXXXXXXXXXXXX

And paste this link to your download program.

Adobe, Microsoft Push Critical Security Fixes

Microsoft today issued 13 patch bundles to fix roughly four dozen security vulnerabilities in Windows and associated software. Separately, Adobe pushed updates to fix a slew of critical flaws in its Flash Player and Adobe Air software, as well as patches to fix holes in Adobe Reader and Acrobat.

Three of the Microsoft patches earned the company’s most dire “critical” rating, meaning they fix flaws that can be exploited to break into vulnerable systems with little or no interaction on the part of the user. The critical patches plug at least 30 separate flaws. The majority of those are included in a cumulative update for Internet Explorer. Other critical fixes address problems with the Windows OS, .NET, Microsoft Office, and Silverlight, among other components.
According to security vendor Shavlik, the issues address in MS15-044 deserve special priority in patching, in part because it impacts so many different Microsoft programs but also because the vulnerabilities fixed in the patch can be exploited merely by viewing specially crafted content in a Web page or a document. More information on and links to today’s individual updates can be found here.

Adobe’s fix for Flash Player and AIR fix at least 18 security holes in the programs. Updates are available for Windows, OS X and Linux versions of the software. Mac and Windows users, the latest, patched version is v. 17.0.0.188. 

If you’re unsure whether your browser has Flash installed or what version it may be running, browse to this link. Adobe Flash Player installed with Google Chrome, as well as Internet Explorer on Windows 8.x, should automatically update to the latest version. To force the installation of an available update, click the triple bar icon to the right of the address bar, select “About Google” Chrome, click the apply update button and restart the browser.

The most recent versions of Flash should be available from the Flash home page, but beware potentially unwanted add-ons, like McAfee Security Scan. To avoid this, uncheck the pre-checked box before downloading, or grab your OS-specific Flash download from here. Windows users who browse the Web with anything other than Internet Explorer may need to apply this patch twice, once with IE and again using the alternative browser (Firefox, Opera, e.g.).

If you run Adobe Reader, Acrobat or AIR, you’ll need to update those programs as well. Adobe said it is not aware of any active exploits or attacks against any of the vulnerabilities it patched with today’s releases.

Reference:
http://krebsonsecurity.com/2015/05/adobe-microsoft-push-critical-security-fixes-7

Microsoft Security Bulletin(s) for May 12, 2015

Today Microsoft released the following Security Bulletin(s).
Note: »www.microsoft.com/techne ··· security and »www.microsoft.com/security are authoritative in all matters concerning Microsoft Security Bulletins! ANY e-mail, web board or newsgroup posting (including this one) should be verified by visiting these sites for official information. Microsoft never sends security or other updates as attachments. These updates must be downloaded from the microsoft.com download center or Windows Update. See the individual bulletins for details.
Because some malicious messages attempt to masquerade as official Microsoft security notices, it is recommended that you physically type the URLs into your web browser and not click on the hyperlinks provided.
Bulletin Summary:
»technet.microsoft.com/li ··· ms15-may
Critical (3)
Microsoft Security Bulletin MS15-043
Cumulative Security Update for Internet Explorer (3049563)
»technet.microsoft.com/li ··· ms15-043
Microsoft Security Bulletin MS15-044
Vulnerabilities in Microsoft Font Drivers Could Allow Remote Code Execution (3057110)
»technet.microsoft.com/li ··· ms15-044
Microsoft Security Bulletin MS15-045
Vulnerability in Windows Journal Could Allow Remote Code Execution (3046002)
»technet.microsoft.com/li ··· ms15-045
Important (10)
Microsoft Security Bulletin MS15-046
Vulnerabilities in Microsoft Office Could Allow Remote Code Execution (3057181)
»technet.microsoft.com/li ··· ms15-046
Microsoft Security Bulletin MS15-047
Vulnerabilities in Microsoft SharePoint Server Could Allow Remote Code Execution (3058083)
»technet.microsoft.com/li ··· ms15-047
Microsoft Security Bulletin MS15-048
Vulnerabilities in .NET Framework Could Allow Elevation of Privilege (3057134)
»technet.microsoft.com/li ··· ms15-048
Microsoft Security Bulletin MS15-049
Vulnerability in Silverlight Could Allow Elevation of Privilege (3058985)
»technet.microsoft.com/li ··· ms15-049
Microsoft Security Bulletin MS15-050
Vulnerability in Service Control Manager Could Allow Elevation of Privilege (3055642)
»technet.microsoft.com/li ··· ms15-050
Microsoft Security Bulletin MS15-051
Vulnerabilities in Windows Kernel-Mode Drivers Could Allow Elevation of Privilege (3057191)
»technet.microsoft.com/li ··· ms15-051
Microsoft Security Bulletin MS15-052
Vulnerability in Windows Kernel Could Allow Security Feature Bypass (3050514)
»technet.microsoft.com/li ··· ms15-052
Microsoft Security Bulletin MS15-053
Vulnerabilities in JScript and VBScript Scripting Engines Could Allow Security Feature Bypass (3057263)
»technet.microsoft.com/li ··· ms15-053
Microsoft Security Bulletin MS15-054
Vulnerability in Microsoft Management Console File Format Could Allow Denial of Service (3051768)
»technet.microsoft.com/li ··· ms15-054
Microsoft Security Bulletin MS15-055
Vulnerability in Schannel Could Allow Information Disclosure (3061518)
»technet.microsoft.com/li ··· ms15-055
Please note that Microsoft may release bulletins out side of this schedule if we determine the need to do so.
If you have any questions regarding the patch or its implementation after reading the above listed bulletin you should contact Product Support Services in the United States at 1-866-PCSafety 1-866-727-2338. International customers should contact their local subsidiary.
As always, download the updates only from the vendors website – visit Windows Update and Office Update or Microsoft Update websites. You may also get the updates thru Automatic Updates functionality in Windows system.
Security Tool
Find out if you are missing important Microsoft product updates by using MBSA.

Reference:
https://technet.microsoft.com/en-us/library/security/ms15-may.aspx
http://blogs.msmvps.com/donpatterson/2015/05/12/microsoft-security-bulletins-for-may-12-2015/

SCCM 2012 Hands-on labs now available online [TechNet Virtual Labs]

MS has recently posted a bunch of virtual labs for Configuration Manager 2012 on the TechNet Virtual Labs homepage. You can work with just about any of the new product features, 90 minutes at a time. I have included a list of links to the online labs below.

TechNet Virtual Lab: Introduction to System Center Configuration Manager 2012

TechNet Virtual Lab: System Center 2012 Configuration Manager: Role Based Administration

TechNet Virtual Lab: System Center 2012 Configuration Manager: Hierarchy Install

TechNet Virtual Lab: System Center 2012 Configuration Manager: Settings Management

TechNet Virtual Lab: System Center 2012 Configuration Manager: Application Management

TechNet Virtual Lab: System Center 2012 Configuration Manager: Content Management

TechNet Virtual Lab: System Center 2012 Configuration Manager: Managing Clients

TechNet Virtual Lab: System Center 2012 Configuration Manager: OSD Bare Metal

TechNet Virtual Lab: System Center 2012 Configuration Manager: Advanced Software Distribution

TechNet Virtual Lab: System Center 2012 Configuration Manager: Basic Software Distribution

TechNet Virtual Lab: System Center 2012 Configuration Manager: Software Updates

TechNet Virtual Lab: System Center 2012 Configuration Manager: Endpoint Protection RC

TechNet Virtual Lab: Migrating from Configuration Manager 2007 to Configuration Manager 2012

File Inventory Report Query by Name, Count and Computer name

Useful script, refer from here : http://eskonr.com/2013/11/sccm-configmgr-reportcount-specific-inventory-file-on-computers/

select cs.Name0 [Computer name],COUNT(*) as [No of Times]
from v_GS_SoftwareFile SF,v_GS_COMPUTER_SYSTEM cs
where FileName like '%.mdf%' and
SF.ResourceID=cs.ResourceID
group by cs.Name0
order by 2 desc

Introducing SCCM 2007 for beginners

Introducing SCCM 2007 for beginners, a starting step to dig in later


As a beginner myself for 'SCCM 2007', I think, I can provide the general view of this concept of System Center Configuration Manager. I have never heard of SCCM before and don’t even know a product of this kind from Microsoft. Initially, when I was introduced to it and heard about its features and advantages, I felt I was lost and cannot catch up to it as I was completely new. But the most striking and cool thing of Microsoft that keeps its competitors run for their money which is its user friendliness and ease of learning and getting used to it. Some of the numerous features and advantages it offer are Distributing packages, Collecting hardware and software inventory, Distributing software updates and Remotely administrating operating systems and even deploying them. Added to these, are some exceptional features like Wake on LAN, Internet based computer management and many more. But let’s go with pure basic and core features for now in the document. With all its features, SCCM by far is the easiest and cool product to reduce the total cost of ownership for large organizations.


Let me remind you, I am a beginner and have no idea on SCCM or SMS before and most of it even now. I just knew that SCCM 2007 is an upgrade of System Management Server 2003 (SMS 2003). I mean to say, to work with SCCM, knowing SMS is not a must, but a bonus.

Keeping in mind the below mentioned, easily understandable components of SCCM will do 90% of our understanding on it.

1) Configuration Manager Client : As the name says, it is any desktop/laptop/server/mobile device that Configuration Manager manages.

2) Configuration Manager Site Server : Server on which configuration manager is installed and that manages Configuration manager site. This site server can be a primary or secondary, the condition for being primary, it needs access to SQL server.

3) Configuration Manager Site System : It is a server which performs one or more Configuration manager roles for a site. There are nine roles that this site system can perform. Management point, Server locator point, Distribution point, reporting point, State migration point, System health Validator point, PXE Server point, Fallback status point and software update point.


Coming to the concept of sites in SCCM, just have a glance of these few lines and that should be it.

A configuration Manager site is defined by SITE BOUNDARIES which can be IP subnets, AD sites or IP ranges and manages the resources with in that boundary.

A configuration manager primary site is the one that can be administered by any site above it in the hierarchy. It can also administer all child sites below it. It should have access to SQL server database. It supports all site system roles.

Configuration manager secondary site doesn’t have access to SQL database and can be managed only by its parent site. But it can manage its child site in the hierarchy.

Configuration manager central site is a primary site that resides on top of the site hierarchy and can administer any site in the hierarchy.


Just few lines back, we read about Configuration manager site system that it performs nine mentioned roles for a site. Let’s get to know about them crisply.

1. Distribution point: As the name suggests, CM site system stores package files and scripts needed for a package to be executed on client machines.

2. Management point : CM clients cannot communicate with CM site server directly and vice versa. This communication is done via Management point.

3. Reporting point : Its a site server that stores report files used for web based reporting functionality for SCCM.

4. Server Locator Point : In lame words, used to locate management Point needed to install client softwares.

5. FallBack Status point : Generally used for debugging. It helps for monitoring and identifying problems during client installations.

6. State migration point : It stores the user's state migration data when a computer's OS is migrated.

7. System health Validator point : Used along side with Network Access Protection feature in SCCM.

8. PXE Service point : It responds to machines requesting for deployment of OS through PXE.

9. Software Updation point : Used along side with Windows Server Update Services(WSUS). For now, it’s responsible for all software updates in the site.


Now that we knew, what SCCM is for, we can easily read and follow any technical document which comes our way.

SCCM Clients installation Troubleshooting Check list

Here is the check list which i have prepared to follow in brief .There may be other issues which are not mentioned here but mostly, issues lies under the below conditions.
There are a variety of Client deployment methods that are available to you when installing the client. Each has its advantages and disadvantages along with the need to meet specific business requirements. 

If you choose to go SCCM client push installation method, Ensure you have created Client push installation account which should have Admin rights on the target computer else it may fail .Client push installation Step by Step Guide is here http://technet.microsoft.com/en-us/library/bb632380.aspx and with Screen shots how to configure from Windows-Noob
Once you initiated the Client push installation from SCCM console( right click on computer,say install client etc ),you can start monitoring CCM.log from your <SCCM installation folder:>\Logs. For more info on how SCCM client push installation works,please refer this article for process and troubleshooting .
The procedure  is same what ever the installation method you choose.The CCMSETUP.EXE will be downloaded to the system (c:\windows\system32\ccmsetup) and is executed. The ccmsetup.exe reads the manifest file (and also mobileclient.tcf) and fetches the remaining files(prerequisites files listed below ) to continue the client installation.

Some of the components that are used in the client deployment process include the following:

• CCMSetup.exe: Used to Install, uninstall and upgrade the SCCM 2007 client using client push installation or manual installation. It is low bandwidth aware and is the single way to launch client deployment. You also do not need to use CCMClean to uninstall the client as the uninstall switch can be used instead. 

• BITS: BITS 2.0 is required for Windows 2000 clients. BITS 2.5 is used for most of the Windows operating systems with the exception of Windows Vista which uses BITS 3.0.
Note: When installing BITS 2.0 on Windows 2000 SP4 machines, a restart is required. This means that if you do not have BITS 2.0, then ccmsetup will stop the install and wait until the next process of reboot before it starts the next process. 

• Microsoft Windows Installer v3.1 v2 (KB 893803): Update to all operating systems except Windows Server 2003 SP1 and later
• Windows Update Agent (WUA) version 7.0.6000.363: Used on clients to support detection of applicable updates and deployment 

• MSXML6.msi - Windows installer script for installing the Core XML Services 

• MSRDC (Remote Differential Compression): Required for branch DP to support binary differential replication. For more information on binary differential replication, please visit http://technet.microsoft.com/en-us/library/bb693953.aspx%20.
Regarding windows 2000 clients, they don't support MSRDC, so Windows 2000 clients cannot be branch DP’s. Windows XP and later will install this utility and the associated windows server code will be used to install the bits. 

• Wimgapi.msi: Imaging API for custom tools for image management 

• CCMSetup.msi: Windows installer package for deploying of the SCCM 2007 client using AD GPO. You cannot run CCMSetup.msi to install clients manually.

You can monitor CCMSETUP.LOG ,CLIENTMSI.LOG from your ccmsetup folder. It will take few min to complete the installation .Once you see, client installation succeeded,You may confirm that,installation is done but it doesn't mean,client is healthy and able to receive policies /send information to Management Point.
Below are the SMS Related services which should (applicability depends on the client perform actions let say BITS is not used when you run the Application from DP) be running on the Client to be healthy all the time..

1. Automatic Updates
2. Background intelligence Transfer service
3. Remote Registry
4. SMS agent Host
5. Terminal Services
6. Windows Installer
7. Windows Management Instrumentation

To know if the client is healthy and able to send /receive polcicies /able to talk to Management point or not ,there are few Log files which you should look into:

CCMSETUP.LOG----->Logs the Client installation activities

ClientLocation.log---->  Records site assignment tasks. Can help to troubleshoot scenarios where the client is not assigned to a Configuration Manager 2007 site.

LocationServices.log---> Records attempts to find management points and distribution points.Can help to troubleshoot scenarios where the client cannot find a management point or distribution point.

AND open the configuration manager Applet from control Panel and go to actions tab,check if you are able to if you are able to see more than 5 policy agents displaying or not which means that client is healthy and sent its inventory information to SCCM site server. You should be able to see the Client with SCCM client Installed and assigned Yes
more information about  SCCM client log files,please refer TechNet
Now its time to do the actual troubleshooting why client is not getting the above policy agents or not reported to SCCM console with Client YES and Installed YES

1.Check the Firewall Enabled or Disabled if enabled,allow the ports to talk to site server.Guide to add Ports to the firewall to allow the required files or policies to download.

2.Check Boundaries (could be (AD site or IP Range or IP Subnet) of the Agent are specified in the site server

3.Schema extension and ensure attributes published into AD system management container (you can see component status if there are any errors while updating the system Management container with attributes)

4.Check the if there no DNS issue in the client and that client is able to resolve the SCCM server NetBIOS as well as FQDN without any issues.

5. Check if the Client is able to talk to Management Point or not using the following Links.
http://<sccm_server>/SMS_MP/.sms_aut?mplist ----should give you blank page
http://<sccm_server>/SMS_MP/.sms_aut?mpcert ---should give you some random numbers

6.Check if WMI is working or not if not try repairing the WMI by stopping WMI service and renaming repository folder (C:\Windows\System32\wbem) and start the service.
If the above test fails make sure that MP is working fine. You can check mpcontrol.log on the site server to find the error and make sure that the same works.

7.Check the Locationservices.log( Finds management points and distribution points) and clientlocation.log( Site assignment tasks) and ClientIDManagerStartup.log(Creates and maintains the client GUID)

If you see anything apart from the above discussed, you may can post the query on  SCCM forums also I would like to hear from you if i miss anything from above steps.

SCCM Client Troubleshooting

When we are working with SCCM we might face multiple issues when we are dealing with SCCM clients below are some of the scenarios and resolutions .

Issue 1

Patches are not installing.

WUAhandler.log

Scan failed with error 0x80244010

(0x80244010 = WU_E_PT_EXCEEDED_MAX_SERVER_TRIPS The number of round trips to the

server exceeded the maximum limit.)

Solution

1.      Take backup of registry key HKLM\Software\Microsoft\Windows\CurrentVersion\InternetSettings\Connections

2.      Delete the invalid proxy (WinHTTPSettings) Registry key.

3.      Allow sometime for the scan to run

Issue 2

Patches are not installing.

WUAhandler.log

Failed to run BeginSearch() on WUAgent. Error = 0x80070422

Solution:-

The service cannot be started, either because it is disabled or because it has no Enabled devices associated with it. We would get this error if the Automatic Updates Service is disabled.

Issue 3

SCCM Client is not installing

Solution

Prerequisite for SCCM.

1.       The login ID should have Admin Access.

2.       following services should automatic and running

a.      BITS

b.      Automatic updates

c.      Distribution transaction coordinator

3.       Following services should be stopped and disabled.

a.      Windows Firewall

4.       minimum 250mb free space in C drive

5.       Latest service pack have to  be installed

6.       System should be on AC power and connected to network.

Issue 4

SCCM Client is not installing

Solution

1.       Local temp folder of the profile is corrupted, clear temp reboot the system and try installing the client.

Issue 5

Configmgr Connection type is currently internet (For Desktop)

Solution

1.       Check the required services status(BITS, Automatic updates, Distribution Transaction Coordinator Service).

2.       Execute SLP CHANGE vbscript we can find it in google

3.       wait for 10 min

Issue 6

System is not reflecting in Console.

Solution

1.       Check the installed package site code.

2.       Check all the tabs appearing in configuration manager ( for desktop 6 Tabs, for Laptops 7 Tabs)

3.       Check for 11 action items in Action tab of Configuration manager properties

4.       If the system has been ghosted, issue may be with GUID,

a.      stop the SMS agent host service

b.      execute GUID change VBSCRIPT which can be found in google

c.      Start the SMS Agent Host Service.

d.      This will take 6 hour to take effect

Issue 7

Only 2 action item in configuration manager Properties, action tab.

Solution

1.       Windows firewall service should be disabled

2.       Port to central and MP server is not opened

Issue 8

Patch download failed

Solution:-

1.       Open Configuration manager properties.

2.       Select Advance Tab

3.       Click Delete files Tab.

4.       Initiate software inventory so that the download will start again.

Manage File and Printer shares, local or on a remote server

RMTSHARE.exe ( Download )

Manage File and Printer shares, local or on a remote server.
Although missing from recent Resource kits, the old version appears to work fine under Windows XP/2003/win7.

Syntax
  Display all shares
      RMTSHARE \\server

  Display details of a specific share
      RMTSHARE \\server\sharename

  Share a Folder 
      RMTSHARE \\server\sharename=drive:path [options]

  Share a Printer 
      RMTSHARE \\server\sharename=printername /PRINTER [options]

  Edit an existing SHARE
      RMTSHARE \\server\sharename [options]

  Delete a SHARE
      RMTSHARE \\server\sharename /DELETE

Options
      /USERS:number 
      /UNLIMITED
      /REMARK:"text"
      /GRANT user:perm
      /REMOVE user

Notes: Either specify /Users to restrict the number of connections that can be made OR specify /UNLIMITED
You can include several /GRANTs in a single command line.
Enclose paths that include spaces like this
\\server\"long share name"="c:\long file name"
An alternative way to list remote shares with PowerShell:

# List the file shares on the remote server: SERVER.

$shares = Get-WmiObject -class Win32_Share -computername SERVER -filter "Type=0"

$shares | foreach {
$path=($_.path)
$Description=($_.Description)
$name=($_.name)
$Caption=($_.Caption)
 
"Share Name   : $name
Source Folder: $path 
Description  : $Description
Caption : $Caption
"
}

Removing collection from the database that didn’t exist in the console

I notice there is some collection missing in console but exist in database. After do some research, it will become an issue while upgrading from SCCM 2007 to SCCM 2012.

First, run sql below:

Select * from collections

Then identified which collection does not appear in console and delete by sql below:

DELETE FROM collections
WHERE CollectionName='Your Collection'

If you are interested to know more about the issue, Check It Out

Warning: It is not supported to modify the ConfigMgr database in any way.