SCCM by Davis: “Moving Applications to the Cloud, 3rd Edition - Book Download” plus 19 more |  |
- Moving Applications to the Cloud, 3rd Edition - Book Download
- Moving Applications to the Cloud, 3rd Edition - Book Download
- Sprint Proposes $2.1 Billion Buyout of Clearwire
- Nash Pherson commented on the post, It’s official! SC 2012 SP1 has RTM’d.
- Chris Nackers wrote a new post, Software updates are displayed as invalid in the Administrator Console in System Center Configuration Manager 2007
- Pleumi became a registered member
- Juniper Boosts SDN Capabilities by Buying Contrail Systems
- Randall Smith posted an update in the group SCCM Right-click tools: Getting a script error running the ping collection tool […]
- Randall Smith joined the group SCCM Right-click tools
- Rod Trent wrote a new post, Tips for submitting a session for MMS 2013
- Craig became a registered member
- SCCM 2012: Silent installation
- Runbook Commander 2.0 released
- Inboxes To Monitor in SCCM
- SMS SCCM WDS MDT Windows 7
- SCCM 2012 Capabilities
- Create a report to show Computer Names, Dell Serial numbers and BIOS versions
- Paul Gonzalez joined the group Enhansoft
- Matt Benninge wrote a new post, It’s official! SC 2012 SP1 has RTM’d.
- SCCM by Davis: “Newcomer Kaazing Upgrades Backbone for Tibco Messaging” plus 19 more
| Moving Applications to the Cloud, 3rd Edition - Book Download Posted: 14 Dec 2012 01:52 AM PST This is a PDF file of the "Moving Applications to the Cloud, Third Edition" book. Moving Apps to the Cloud 3rd Edition.pdf 3.4 MB | ||||||||||||||||||||||||||
| Moving Applications to the Cloud, 3rd Edition - Book Download Posted: 14 Dec 2012 01:52 AM PST This is a PDF file of the "Moving Applications to the Cloud, Third Edition" book. Moving Apps to the Cloud 3rd Edition.pdf 3.4 MB | ||||||||||||||||||||||||||
| Sprint Proposes $2.1 Billion Buyout of Clearwire Posted: 13 Dec 2012 08:15 PM PST Sprint filed paperwork with the SEC proposing a $2.1 billion buyout of Clearwire that will finally give it control over major spectrum. | ||||||||||||||||||||||||||
| Nash Pherson commented on the post, It’s official! SC 2012 SP1 has RTM’d. Posted: 13 Dec 2012 06:48 PM PST Does this really constitute and 'official' announcement? Comments: 0 | ||||||||||||||||||||||||||
| Posted: 13 Dec 2012 04:29 PM PST
Comments: 0 | ||||||||||||||||||||||||||
| Pleumi became a registered member Posted: 13 Dec 2012 02:06 PM PST Comments: 0 | ||||||||||||||||||||||||||
| Juniper Boosts SDN Capabilities by Buying Contrail Systems Posted: 13 Dec 2012 01:10 PM PST Juniper is spending $176 million to acquire Contrail, which has been developing a network compiler for software-defined networks. | ||||||||||||||||||||||||||
| Posted: 13 Dec 2012 10:16 AM PST Getting a script error running the ping collection tool (80041001). Anyone else seeing this? The file is CA.hta. Line 316, character 9. Comments: 0 | ||||||||||||||||||||||||||
| Randall Smith joined the group SCCM Right-click tools Posted: 13 Dec 2012 10:11 AM PST Comments: 0 | ||||||||||||||||||||||||||
| Rod Trent wrote a new post, Tips for submitting a session for MMS 2013 Posted: 13 Dec 2012 09:37 AM PST With the Call for MMS 2013 Content now live, there are those of you who are wondering what it takes to submit a session topic that will be picked from the hundreds of submissions. When submitting your session, […] Comments: 0 | ||||||||||||||||||||||||||
| Craig became a registered member Posted: 13 Dec 2012 08:16 AM PST Comments: 0 | ||||||||||||||||||||||||||
| SCCM 2012: Silent installation Posted: 25 Oct 2012 06:29 AM PDT A good guide (including silent SQL installation, silent Admin Console installation and silent Primary site installation) is in Sandbu blog | ||||||||||||||||||||||||||
| Runbook Commander 2.0 released Posted: 21 Oct 2012 10:46 AM PDT Second version of this helpful tool is released. Here are the changes compared to version 1.0: Support for Configuration Manager 2007 – RBC 2.0 now supports both Configuration Manager 2007 and 2012 Configuration Manager. Additionally when deploying Runbook Commander bundled with pre-created XML files the installer will determine what version on Configuration Manager Console is being used and appropriately stage the XML extensions files. New XML Generator Tool – RBC requires custom XML files to be created for each environment. These XML files controll which Orchestrator Runbooks are available for execution from the Configuration Manager environment. The new XML Generator tool handles the XML creation for Configuration Manager 2007 and 2012 Configuration Manager. This tool now also allows saving off XML files for use in a pre-staged deployment (see next bullet point). Finally the XML GEN tool has been redesigned for an easier interactive experience. New Installer – with RBC version 1, the installer basically staged the computer for use with RBC. It was then up to the individual to run the XML generator tool on each machine in order to create the console extension. Alternatively the XML files could have been manually (or scripted) copied to the appropriate location on the target computer. New to version 2, the console extensions XML files can be pre-created and then deployed with RBC allowing for a single and automated installation experience across many computers. Replace XML Application – RBC 2.0 includes a new application that can be deployed to computers which will replace the console extensions XML. In the situation where new Runbooks need to be added to RBC or old Runbooks need to be removed from RBC, the custom XML would be created using the XML generator tool and then deployed to all machines with the Replace XML application. The replace XML application will appropriately replace the console extension XML and at next launch the Configuration Manager console will be loaded with the updated set of Runbooks. Console Extensions to the Program Node – RBC Version 1 had support for consoles extensions for devices and collections. I had received a request to add programs which has been completed. I will add more console items as time permits with priority going to those requested. Drop Down Lists – Added to version 2.0 is the ability to dynamically create drop down lists as parameter values. This will allow the Runbook administrator to provide a list of values on the actual Runbook. These values will then be available from RBC at execution time from the Configuration Manager console. I will detail the creation of these in the soon to complete full documentation. Fixed IIS Paging Limitation – The Orchestrator Web Service contains a paging mechanism which allows only 50 Rubooks (or other objects) to be retuned at query time. With RBC V1.0 the XML Gen tool would not return all available Runbooks without making modification to the IIS Web Service application settings. The XML GEN 2.0 includes code that gets around the paging feature and will now present all Runbooks at execution time. Removed Start Menu Shortcuts – As RBC is for the most part initiated from within the Configuration Manager console all start menu shortcuts have been removed. This does mean that if using the XML generator application you will need to navigate to the installation folder and execute directly. This process will be detail in the forthcoming configuration and deployment guide. Download the new version from here. | ||||||||||||||||||||||||||
| Posted: 19 Oct 2012 02:59 PM PDT ConfigMgr 2007 inboxes with a backlog of files to be processed generally indicates a problem is occurring. As a result your infrastructure may suffer and may become problematic. Listed here is a list of the ConfigMgr 2007 inboxes that should be checked on a regular basis to ensure that your site function as expected. Auth\Dataldr.Box A backlog of files can indicate problems accessing the site database. Auth\Dataldr.Box\Process A backlog of files can indicate problems accessing the site database. Auth\Ddm.box\Bad_DDRs A backlog of files can indicate a network corruption problem or a problem with the DDM Auth\Sinv.Box A backlog of files can indicate that the Software Inventory Processor cannot connect to the site database or that too many files were received. Auth\Sinv.Box\Orphans A backlog of files can indicate problems with specific clients, with management points, or with the network that could cause data corruption. Compsumm.Box A backlog of files can indicate that the Component Status Summarizer cannot process the volume of messages. Dataldr.Box A backlog of files can indicate problems accessing the Systems Management Server (SMS) database Dataldr.Box\Badmifs A backlog of files can indicate a bad custom MIF file or that a client computer cannot transfer the file correctly. Ddm.Box A backlog of files can indicate a bad DDR is preventing other DDR's to process. Ddm.Box\Bad_DDRs A backlog of files can indicate a network corruption problem or a problem with the DDM OfferSum.Box A backlog of files can indicate a performance problem that is caused by a large number of messages. Policypv.Box A backlog of files in the policypv.box folder indicates that the policy provider component is not running. Replmgr.Box\Ready A backlog of files can indicate that the Scheduler is backlogged or is already processing files of the same priority Schedule.Box A backlog of files can indicate that the Sender cannot connect to or cannot transfer data to another site. Schedule.Box\Outboxes A backlog of .srq files indicates that the sender cannot process the number of jobs scheduled for that sender or that the sender cannot connect to or transfer data to another site. Schedule.Box\Tosend A backlog of files can indicate that many send requests are not completed or that the Scheduler has not yet deleted the files. Sinv.Box A backlog of files can indicate that the Software Inventory Processor cannot connect to the site database or that too many files were received. Sinv.Box\BadSinv A backlog of files can indicate problems with specific clients, with management points, or with the network, causing data corruption. SiteStat.Box A backlog of files can indicate a performance problem. Examine status messages for the Site System Status Summarizer for possible problems. Statmgr.Box\Futureq A backlog of files can indicate that some site systems' clocks are not synchronized with the site server. Statmgr.Box\Queue A backlog of files can indicate a problem with the Status Manager or that the component is trying to process too many messages. Statmgr.Box\Retry A backlog of files can indicate problems with the connection to the computer that is running SQL Server. Statmgr.Box\Statmsgs A backlog of files can indicate a problem with the Status Manager or that the Status Manager is trying to process too many messages Swmproc.Box A backlog of .sum and .sur files can indicate that the Software Metering Processor component cannot connect to the SMS database. Additional Information: Inbox Folders in Configuration Manager 2007 http://technet.microsoft.com/en-us/library/bb892790.aspx Count Files In All The SMS inboxes And Send To Excel http://myitforum.com/cs2/blogs/dhite/archive/2006/07/23/22467.aspx VBS Script To Count Objects In A Specified SMS Or ConfigMgr Inbox VBS Script To Count Objects In A Specified SMS Or ConfigMgr Inbox From A List Of Servers VBS Script To Count Objects In Specified SMS Site Server Inbox | ||||||||||||||||||||||||||
| Posted: 16 Oct 2012 05:06 AM PDT Tips- How to package softwareSwitches-r
Packagescmd files must have drive letter Useful silent (un)install code:
IMAGExEnter "imagex /info img_file", where "img_file" represents the location of the WIM file. You should see now the description of the WIM file as an XML file. The name of the tag for the image number is IMAGE INDEX. Create a new folder where the image shall be mounted. This is the image path. Now, you can mount the image: imagex /mount img_file img_number img_path imagex /mountrw img_file img_number img_path Once you've modified the image you can unmount it with this command: imagex /unmount /commit img_path DISMdism /Mount-Wim /wimfile:d:\boot.wim /index:1 /MountDir:d:\mount http://technet.microsoft.com/en-us/library/dd744360%28v=ws.10%29.aspxdism /Mount-Wim /wimfile:"E:\DeploymentShare\Operating Systems\Windows7x64-Aug12\Windows7x64.wim" /index:1 /MountDir:e:\mount
Add Drivers to Vista Boot Image1. Update the WDS boot image to include the new third-party network driver. To do this, follow these steps. Note The following procedure assumes that the Windows Automated Installation Kit (AIK) is installed on the WDS server. If the Windows AIK is not installed on the WDS server, you can perform the same procedure on another computer that does have the Windows AIK installed. Then, map a network drive to the WDS server.
Note X is the boot index number. The number indicates that image number X is marked as bootable and that the image is to be updated. The second image is the default image that you would typically modify. However, always verify which image is marked as bootable.
—-
Labels: Microsoft deployment Toolkit (MDT)Instructions: How to deploy and Windows server 2003 image to bare metal (set to capture the file at the end of the task sequence) 1 On the computer you wish to deploy an OS instance power on and press F12 when prompted. Select network boot (PXE boot). Be ready to press F12 again when prompted otherwise it will time out and proceed to the next item in the boot order. Proceeding will Format the computer and delete all data! How to sysprep and capture a current image. 1 On the computer you wish to capture click Start > Run and type \\contoso\DeploymentShareEng$\scripts\LiteTouch.vbs | ||||||||||||||||||||||||||
| Posted: 15 Oct 2012 12:11 AM PDT I was trying to search for some new capabilities of SCCM, I contacted Microsoft and got the following information from them. Some capabilities you need to know:
Positioning SCCM in the Market: I would like to mention Microsoft is the Leader in Magic Quadrant for Client Management Tools.
What Gartner Wrote about SCCM: Microsoft System Center Configuration Manager (ConfigManager) is the dominant product in the market; it holds more than half of the market's installed base. Microsoft continues to make ConfigManager financially attractive by including the client management licenses (MLs) in the Microsoft Core CAL and Enterprise CAL Suites, bundling ConfigManager with related products such as ForeFront Endpoint Protection and Service Manager. Microsoft will release ConfigManager 2012 in the first half of 2012. ConfigManager has never been a best-of-breed product, but the 2012 release narrows the gap between it and competitive products. First, the complexity of the ConfigManager infrastructure is reduced in the 2012 version through the introduction of role-based access controls and other capabilities that reduce the amount of traffic required to travel the network. The new version also requires less scripting to execute common tasks. Finally, ConfigManager moved to a more context-aware model. The tool now delivers applications to users, and will present different applications and use different delivery models based on user context (e.g., if they are using their primary laptop or using a terminal server session). This model requires significant changes to IT processes around software licensing and software delivery, so uptake among early adopters of this feature has been low. Microsoft also released Intune, a separate SaaS-based client management product, but Gartner has seen little uptake of the product at this point. Intune will be appropriate for small to midsize organizations that have basic requirements, but organizations that require full life cycle management and customization should continue to use ConfigManager. Strengths: 1. ConfigManager 's integration with App-V is tight. The App-V client can pull App-V applications from ConfigManager distribution points on an on-demand basis. 2. Microsoft has developed tight integration with products in important companion areas — for example, System Center Service Manager and Forefront Endpoint Protection. 3. Because of Microsoft's large installed base, there is much more knowledge of ConfigManager in the industry than of competitive products; it's easier to find consultants, contractors, IT personnel and active user communities for ConfigManager than for other products. Cautions: 1. While ConfigManager 2012 will provide lightweight mobile device management through Exchange ActiveSync, many organizations will opt for third-party MDM products, or will select alternative client management vendors that offer more comprehensive capabilities. 2. ConfigManager does not support Mac OSX or Linux desktop. (Review what is new in SP1?) 3. While the product has been simplified, ConfigManager is still complex; it requires deep expertise to implement and use successfully. What is New in SP1 for System Center 2012 – Configuration Manager 2012: There are a lot of changes will be included in Microsoft System Center 2012 – Configuration Manager: One of the most significant changes is support for Windows 8. Configuration Manager SP1 supports Windows 8 in the following ways: 1. You can install the Configuration Manager client on Windows 8 computers and deploy Windows 8 to new computers or to upgrade previous client operating versions. Configuration Manager also supports Windows To Go. 2. Configuration Manager supports Windows 8 features, such as metered Internet connections and Always On Always Connected. 3. You can configure user data and profiles configuration items for folder redirection, offline files, and roaming profiles. 4. You can configure new deployment types for Windows 8 applications, which support standalone applications (.appx files) and links to the Windows Store. Other significant changes include the following: 1. Support for Windows Server 2012 and SQL Server 2012. 2. Clients are now supported on Mac computers, and on Linux and UNIX servers. 3. Windows PowerShell cmdlets are available to automate Configuration Manager Operations by using Windows PowerShell scripts. 4. Support for cloud services, including a new distribution point for Windows Azure. 5. More flexible hierarchy management with support to expand a stand-alone primary site into a hierarchy that includes a new central administration site, and the migration of a Configuration Manager SP1 hierarchy to another Configuration Manager SP1 hierarchy. 6. Support for multiple software update points for a site to provide automatic redundancy for clients in the same way as you can configure multiple management points. 7. Client notification to initiate some client operations from the Configuration Manager console, which include downloading computer policy and initiating a malware scan to be performed as soon as possible, instead of during the normal client policy polling interval. 8. Support for virtual environments that allow multiple virtual applications to share file system and registry information instead of running in an isolated space. 9. Email alert subscriptions are now supported for all features, not just Endpoint Protection. | ||||||||||||||||||||||||||
| Create a report to show Computer Names, Dell Serial numbers and BIOS versions Posted: 14 Oct 2012 07:19 AM PDT Below is a query I used for the report, since I'm a novice when it comes to SQL I searched for some help and can across a great blog post which helped me create my report. http://myitforum.com/cs2/blogs/jmarcum/archive/2011/05/19/157675.aspx – Many Thanks!! I also download the documentation for "Creating Custom Reports by Using Configuration Manager 2007 SQL Views" from here Once I had what I needed I created the report, below are the details "SELECT TOP (100) PERCENT dbo.v_R_System.Netbios_Name0 AS Computer, dbo.v_GS_PC_BIOS.SMBIOSBIOSVersion0 AS [BIOS Version], dbo.v_GS_PC_BIOS.SerialNumber0 AS [Dell Serial Number] FROM dbo.v_GS_PC_BIOS INNER JOIN dbo.v_R_System ON dbo.v_GS_PC_BIOS.ResourceID = dbo.v_R_System.ResourceID ORDER BY Computer" Once I had this I started the New Report wizard from Reporting under Computer Management and pasted the above into SQL Statement area and accepted all defaults, I ran the report and it gave me the information I needed.
| ||||||||||||||||||||||||||
| Paul Gonzalez joined the group Enhansoft Posted: 13 Dec 2012 07:21 AM PST Comments: 0 | ||||||||||||||||||||||||||
| Matt Benninge wrote a new post, It’s official! SC 2012 SP1 has RTM’d. Posted: 13 Dec 2012 06:07 AM PST
It's official! SC 2012 SP1 has RTM'd. Few notes to make the upgrade path crystal clear: General […] Comments: 0 | ||||||||||||||||||||||||||
| SCCM by Davis: “Newcomer Kaazing Upgrades Backbone for Tibco Messaging” plus 19 more Posted: 13 Dec 2012 02:07 AM PST
System Center Configuration Manager - Davis Blog  | ||||||||||||||||||||||||||
| You are subscribed to email updates from SCCM by Davis To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
| Google Inc., 20 West Kinzie, Chicago IL USA 60610 | |
No hay comentarios:
Publicar un comentario