Duration: 50 minutes 39 seconds
Size: 14.5MB
Watch Adam's video on DNRTV on these rules:
Part A (53:13) - 181MB
Part B (49:12) - 171MB
Part C (42:19) - 158MB
Enhanced System and User Discovery Tools, out of the box, SMS 2003 does a pretty good job of discovering systems from Active Directory. It's not perfect, though—there are a few gaps in its methods. The Enhanced System Discovery tool, assists in filling these gaps. Out of the box, SMS 2003 does not perform Windows NT 4 domain discovery. This tool solves that by enumerating all machines from a list of NT 4 domains, resolving their IP addresses from DNS or WINS, and creating data discovery records for each system. (http://www.systemcentertools/)
BITS Bandwidth Manager is an SMS Installer script that lets you throttle BITS bandwidthon Windows XP SP2 systems. You do not need to manually adjust any settings. The script takes care of the Registry key manipulation for you.(http://www.myitforum.com/inc/upload/11332BITSManager.zip)
1E SMSWakeUp: this WOL product is able to turn on computers after they have been shut down by users. The wake cycle can be triggered on a regular schedule to power up systems in preparation for the workday, or to perform software deployment activities. (http://www.1e.com/)
1E NightWatchman: Since we are talking about waking systems that have been shut down, it maybe a good practice to examine how best to shut down those systems in the first place. Why dowe want to shut down systems? We do this to enforce reboot cycles and to save energy costs. (http://www.1e.com/)
1E SMSNomad Branch: Some offices may not have the server hardware to allow for a Distribution Point (DP). But those offices may have a substantial number of users and/or be separated from the rest of the network by a low-speed or saturated WAN link, which you would rather not send multiple copies of a package across. SMSNomad Branch acts similar to a peer-to-peer network, allowing other computers to become DPs. If one machine is shutdown, another is selected as the DP. Included in this technology is multicast, increasing its efficiency to reduce network traffic on the local network segment. (http://www.1e.com/)
1E OSD Plus Pack: This is an enhancement to the SMS OSD Feature Pack. It allows you to leverage the SMS OSD Feature Pack in offices that do not have DPs. OSD Plus Pack offers similar functionality to SMSNomad Branch, but also has a few other applications bundledwith it: State Migration Editor, which is an interface for the User State Migration Tool, AppMigrator, which allows the automatic reinstallation of applications after OS imaging, PXE Lite, which is a local PXE server to allow deployment of OS images to bare-metalmachines booted from the network PXE server. (http://www.1e.com/)
SMS Companion 2006: This product provides WOL capabilities, similar to 1E's SMSWakeUp, but leverages slightly different technologies behind the scenes. A key difference is that SMS Companion puts systems in hibernation, rather than powering them off. The following are some of the key applications included with this product:Wake-on-Schedule: Allows clients to come out of a hibernation state. Service Windows: Allows you to restrict the SMS inventory and software distributions from happening during specific time periods, to reduce or eliminate user interruptions. Load Balancing: Allows you to reduce peak network and SMS server loading by making sure that the clients use these resources in a controlled manner. (http://www.smsexpert.com/)
Quest Management Xtensions for SMS: Since Windows platforms are not the only systems in an enterprise, you may need a way tomanage other platforms, such as Unix, Linux, and Mac OS X. These management extensions offer that capability for SMS 2003. One of the unique aspects of this product is its support route: first-level support is handled by Microsoft Product Support Services. (http://www.quest.com/quest-management-xtensions-for-sms)
Detailed Feature Comparison of ESD 2007, SMS 2003 and SCCM 2007
| Feature | ESD 2007 | SMS | SCCM 2007 |
| Ability to extend discovery with additional AD Attributes | Yes | No | Yes |
| Ability to filter on the when changed attribute | Yes | No | No |
| Delta Discovery – Only Discover AD Objects that have changed since the last discovery | Yes | No | No |
| Update Collection Membership Automatically when AD Group membership changes. New in R2! | Yes | No | No |
| Discover only systems assigned to specific sites | Yes | No | No |
| Run the discovery agent on a workstation reducing SMS/SCCM Server load | Yes | No | No |
Don't you think it's time to tie the knot?
- Is SMS/SCCM continually discovering and troubleshooting inactive systems from Active Directory? How about disabled systems?
- Do your patch compliance reports indicate less compliance due to a large percentage of inactive systems?
- Is your organization paying for licenses they aren't using because of inactive systems being counted towards your Software Licensing Agreements?
- Does it take hours or days for SMS/SCCM to update based on changes to systems in Active Directory?
- Do you need to deploy software to systems immediately after they have changed OU's or been added to a new Active Directory group?
- Are your site servers flooded with discovery records? Does it take all night or all weekend to complete an Active Directory discovery cycle?
Don't you think it's time to tie the knot?
 | ||
| This tool is designed to allow an SMS Administrator to Migrate all or selected packages and programs from his SMS environment into a System Center Configuration Management (ConfigMgr) environment. The tool has the following features:-
| ||
RSHUT Pro is very usefull when you want to stop your system shuting down count time...
SCCM Duplicate System Entries in the Console
If your SCCM console has duplicated System entries in the Console, and you want to find it right? Below is the Query for this issue.
select R.ResourceID,R.ResourceType,R.Name,R.SMSUniqueIdentifier,R.ResourceDomainORWorkgroup,R.Client from SMS_R_System as r full join SMS_R_System as s1 on s1.ResourceId = r.ResourceId full join SMS_R_System as s2 on s2.Name = s1.Name where s1.Name = s2.Name and s1.ResourceId != s2.ResourceId
We can use WMIC tool to run on remote computers and get the client actions as we want
Some examples to trigger SMS/SCCM Client Actions from command line:
Disable Software-Distribution:
WMIC /namespace:\\root\ccm\policy\machine\requestedconfig path ccm_SoftwareDistributionClientConfig CREATE ComponentName="Disable SWDist",Enabled="false",LockSettings="TRUE",PolicySource="local",PolicyVersion="1.0" ,SiteSettingsKey="1" /NOINTERACTIVE
Re-Activate Software-Distribution:
WMIC /namespace:\\root\ccm\policy\machine\requestedconfig path ccm_SoftwareDistributionClientConfig WHERE ComponentName="Disable SWDist" delete /NOINTERACTIVE
Trigger Hardware Inventory:
WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000001}" /NOINTERACTIVE
Trigger Software Inventory:
WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000002}" /NOINTERACTIVE
Trigger DataDiscoverRecord (DDR) update:
WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000003}" /NOINTERACTIVE
Force a FULL HW Inventory on next HW-Inv Schedule:
WMIC /namespace:\\root\ccm\invagt path inventoryActionStatus where InventoryActionID="{00000000-0000-0000-0000-000000000001}" DELETE /NOINTERACTIVE
Repair SMS/SCCM Agent on a remote client:
WMIC /node:%MACHINE% /namespace:\\root\ccm path sms_client CALL RepairClient
Repair a list (all clients listed in clients.txt) of remote SMS/SCCM Agents:
WMIC /node:@clients.txt /namespace:\\root\ccm path sms_client CALL RepairClient
Collections
.SiteID,
Collections.CollectionName,
Collection_Rules.QueryName,
Collection_Rules_SQL.WQL,
Collection_Rules_SQL.SQLFrom
Collections,Collection_Rules, Collection_Rules_SQLWhere
Collections
.CollectionID = Collection_Rules.CollectionIDAND
Collections.CollectionID = Collection_Rules_SQL.CollectionID-------------------1. Most of the tools that were included in the original SMS Console Additions V1.4
2. The ability to see the computer details and security compliance web reports for a single client inside collections
3. A separate drill down for client logs as well as security update client logs.
4. The ability to check the status of an advertisement with a right click from that advertisement In order to get the client and the advertisement web reports to work you must perform the following.
5. Fixed the right click tools on the "collections" that didn't open a CMD window when running. Also fixed the echo so the results now show up in a command window
6. Will detect the version of the tool installed so re-installation of unnecessary files does not occur when new versions are released
7. Now has an entry in Add Remove Programs which enables un-installation of the program
8. No more hard coding of your site code to get scripts and reports to run correctly
For a Copy a Folder
Dim wShell
strComputer = "."
Set objWMIService = GetObject _
("winmgmts:\\" & strComputer & "\root\cimv2:Win32_Process")
'errReturn = objWMIService.Create _
' ("cmd.exe /c md c:\ups", Null, Null, intProcessID)
Set objFSO = CreateObject("Scripting.FileSystemObject")
objFSO.CopyFolder "file://172.20.128.51/sms_uk/Oct 2008\*.*" , "c:\pav\" , OverwriteExisting
Set wShell = CreateObject("WScript.Shell")
'wShell.Run "c:\ups\Election.html"
Const OverwriteExisting = TRUE
-------------------
Thanks,
http://sccm07.blogspot.com/
Select DISTINCT Model0 from Computer_System_DATA
The above one will show all the Models
The below Query will show everything in the Database
Select
* from Computer_system_dataUsing an editor such as Windows Group Policy editor, open a new or existing Group Policy object.
In the Group Policy editor, navigate to Computer Configuration / Administrative Templates / Windows Components / Windows Update, and then open the properties of the setting Specify intranet Microsoft update service location.
Click Enabled.
In the Set the intranet update service for detecting updates: field, specify the name of the software update point server you want to use, and the port. These must match exactly with the server name format and the port being used by the software update point:
If the site is in mixed mode and software updates is using a custom Web site, the port number is likely to be 8530 unless it has been changed.
If your WSUS Setup configured on port 8530 then the below URL will be placed
In the Set the intranet statistics server: field, specify the name of the intranet statistics server you want to use. There are no specific requirements for specifying this server. It does not have to be the same computer as the software update point server, and the format does not have to match if it is the same server.
Assign the Group Policy object to the computers on which you want to install the Configuration Manager client and receive software updates.
In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Site Management / <site code> – <site name> / Site Settings / Client Installation Methods.
Right-click Software Update Point Client Installation, and click Properties.
To enable client installation, select the Enable Software Update Point Client Installation check box.
If the client software on the Configuration Manager 2007 site server is a later version than the client version stored on the software update point, the Upgrade Client Package Version dialog box will open. Click Yes to publish the most recent version of the client software to the software update point.
To finish configuring the software update point client installation, click OK.
First command to start with Powershell is
Power Shell Learning Commands:-
dir -RECURSE
`
Start-Transcript filename.txt
stop-Transcript
I will post to continue this article persistently
-----------------------------------------------------------------------------------------------------------------------------------
SQL Query:-->
-----------------------------------------------------------------------------------------------------------------------------------
To know the package Name and ID
SELECT PackageID, Name
FROM dbo.v_Package
-----------------------------------------------------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------------------------------------------------
SQL Query:-->
If you want to filter with the package ID then modify the Query to
SELECT PackageID, Name
FROM dbo.v_Package
WHERE (PackageID = 'YourPKGID')
-----------------------------------------------------------------------------------------------------------------------------------
-------------------
Thanks,
http://sccm07.blogspot.com/
Select * from pkgservers where NALpath like '%\\retired DP path\DP$'
Select * from pkgstatus where pkgserver like '%\\retired DP path\DP$'
by runing above two commands verifiy that you have got the correct Correpted DP package ID or not. then if you find it you can safly run the below two commands to delete.
Next delete entries from any of the above tables to the invalid dp share.
Delete from pkgservers where NALpath like '%\\retired DP path\DP$'
Delete from pkgstatus where pkgserver like '%\\retired DP path\DP$'
| Log File Name | Description | ||
| CCMSetup.log | Provides information about client-based operating system actions. | ||
| CreateTSMedia.log | Provides information about task sequence media when it is created. This log is generated on the computer running the Configuration Manager 2007 administrator console. | ||
| DriverCatalog.log | Provides information about device drivers that have been imported into the driver catalog. | ||
| MP_ClientIDManager.log | Provides information about the Configuration Manager 2007 management point when it responds to Configuration Manager 2007 client ID requests from boot media or PXE. This log is generated on the Configuration Manager 2007 management point. | ||
| MP_DriverManager.log | Provides information about the Configuration Manager 2007 management point when it responds to a request from the Auto Apply Driver task sequence action. This log is generated on the Configuration Manager 2007 management point. | ||
| MP_Location.log | Provides information about the Configuration Manager 2007 management point when it responds to request state store or release state store requests from the state migration point. This log is generated on the Configuration Manager 2007 management point. | ||
| Pxecontrol.log | Provides information about the PXE Control Manager. | ||
| PXEMsi.log | Provides information about the PXE service point and is generated when the PXE service point site server has been created. | ||
| PXESetup.log | Provides information about the PXE service point and is generated when the PXE service point site server has been created. | ||
| Setupact.log Setupapi.log Setuperr.log | Provide information about Windows Sysprep and setup logs. | ||
| SmpIsapi.log | Provides information about the state migration point Configuration Manager 2007 client request responses. | ||
| Smpmgr.log | Provides information about the results of state migration point health checks and configuration changes. | ||
| SmpMSI.log | Provides information about the state migration point and is generated when the state migration point site server has been created. | ||
| Smsprov.log | Provides information about the SMS provider. | ||
| Smspxe.log | Provides information about the Configuration Manager 2007 PXE service point. | ||
| SMSSMPSetup.log | Provides information about the state migration point and is generated when the state migration point site server has been created. | ||
| Smsts.log | General location for all operating system deployment and task sequence log events.Log file location:· If task sequence completes when running in the full operating system with a Configuration Manager 2007 client installed on the computer: <CCM Install Dir>\logs· If task sequence completes when running in the full operating system with no Configuration Manager 2007 client installed on the computer: %temp%\SMSTSLOG· If task sequence completes when running in WindowsPE: <largest fixed partition>\SMSTSLOG
| ||
| TaskSequenceProvider.log | Provides information about task sequences when they are imported, exported, or edited. | ||
| USMT Log loadstate.log | Provides information about the User State Migration Tool (USMT) regarding the restore of user state data. | ||
| USMT Log scanstate.log | Provides information about the USMT regarding the capture of user state data. |
When using RDP you may not be able to cut and paste information between your local and remote sessions.
Cause:
The rdpclip.exe processing may not be running on the remote system. Alternatively, the clipboard chain may be incomplete.
Workaround:
Restart the rdpclip.exe process on the remote system.
More Information:
The following article has a good article on Clipboard chaining;
http://blogs.msdn.com/ts/archive/2006/11/16/why-does-my-shared-clipboard-not-work-part-1.aspx
