1. Open Run Command by pressing Win+r keyboard shortcut
2. Navigate to following Registry key:
HKEY_LOCAL_MACHINESoftwareBrowserChoice
3. Now create new registry with
Value name: Enable
Value type: DWORD
4. Now if you do not want to display the Browser Choice update then enter value of above key as “0″
and If you want to display the Browser Choice update (default) set value to “1″
See KB2019411
1. Backup the database.
2. Find the entries for the DP package share:
Select * from pkgservers where NALpath like ‘%\<server>%’
Select * from pkgstatus where pkgserver like ‘%\<server>%’
Select * from contentdpmap where serverpath like ‘%\<server>%’
Select * from DPinfo where servername like ‘%<server>%’
3. Delete any entries from any of the above tables that point to the nonexistent share:
Delete from pkgservers where NALpath like ‘%\<server>%’
Delete from pkgstatus where pkgserver like ‘%\<server>%’
Delete from contentdpmap where serverpath like ‘%\<server>%’
Delete from DPinfo where servername like ‘%<server>%’
Keep in mind – This metod is NOT supported by Microsoft
error:
SMS Site Component Manager failed to deinstall all SMS server components from site system “\servername“.
SMS Site Component Manager failed to reinstall this component on this site system.
If logging is enabled for the SMS_SITE_COMPONENT_MANAGER service, entries similar to the following are found in the SmsLogsSitecomp.Log file:
Change the value of Deinstallation Start Time to 1. Stop and restart the SMS_SITE_COMPONENT_MANAGER service on the Site Server to force a Site Component Manager update cycle. The Site Component Manager log should indicate the deinstallation process has timed out as follows:
The error:
MP Control Manager detected MPsetup has failed to create the CCM_Incoming Virtual Directory.
Possible cause: The IIS IWAM account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IWAM account. (i.e.: “net user IWAMMachineName)
Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use “net user” to modify the account properties.
Possible cause: The IIS IUSR account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IUSR account. (i.e.: “net user IWAMMachineName)
Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use “net user” to modify the account properties.
Possible cause: The designated Web Site is disabled in IIS.
Solution: Verify that the designated Web Site is enabled, and functioning properly.
Solution:
This worked for me:
1. Remove BITS
2. Reboot
3. Add BITS
4. Trigger installation (Stop and Start SMS_SITE_COMPONENT_MANAGER using the ConfigMgr Service Manager)
Windows only: Ever wonder why your laptop’s battery seems to die too quickly? The Windows Help blog points out a hidden command-line switch that generates a report with loads of helpful troubleshooting information.
The report lists all of the devices that are causing problems with sleep mode, explains the different power saving modes your computer supports, and even gives you detailed information on your battery—invaluable information when your system takes forever to go in and out of sleep mode. Generating the report is easy enough—just open up a command prompt in administrator mode using the context menu -> Run as Administrator option, and then type in the following:
powercfg -ENERGY
The utility will take a while to generate the report, sometimes more than the 60 seconds it quotes you—but when it finishes you can open up the generated file in your favorite web browser. Once you’ve examined the report, you can figure out if you need to do some tweaking or update a driver.
Windows 7 includes a little-known new feature called Virtual Wi-Fi, which effectively turns your PC or laptop into a software-based router. Any other Wi-Fi-enabled devices within range – a desktop, laptop, an iPod perhaps – will “see” you as a new network and, once logged on, immediately be able to share your internet connection.
This will only work if your wireless adapter driver supports it, though, and not all do. Check with your adapter manufacturer and make sure you’ve installed the very latest drivers to give you the best chance.
Once you have driver support then the easiest approach is to get a network tool that can set up virtual Wi-Fi for you. Virtual Router (below) is free, easy to use and should have you sharing your internet connection very quickly.
If you don’t mind working with the command line, though, maybe setting up some batch files or scripts, then it’s not that difficult to set this up manually. See Turn your Windows 7 laptop into a wireless hotspot for more.
“Disk2vhd” is a new utility released by Sysinternals team at Microsoft which allows you to create VHD versions of physical disks. If you are not aware of these technical terms, lets help you in understanding them.
VHD refers to “Virtual Hard Disk” which is a file format used in Microsoft virtual machines. So by using “Disk2vhd” you can create VHD versions of your HDD which can be used in Microsoft Virtual PC or Microsoft Hyper-V virtual machines (VMs).
Disk2vhd supports Windows XP SP2 and higher including 64-bit editions.
You can download it using following link:
Privacy features such as InPrivate browsing in Internet Explorer 8 and similar features in Chrome and Firefox promise to protect your privacy by not keeping track of page history, temporary files and cookies. This may be enough to hide your tracks from a beginner computer user but there are still traces of what sites you visit within the local DNS cache. An advanced user can run the ipconfig /displaydns command to view the most recent sites visited.
For example, when you start InPrivate browsing in Internet Explorer and visit Bing.com.
The DNS Cache shows where you have been.
The best way to improve the privacy of your InPrivate browsing sessions is to also clear the local DNS cache after closing the browser. Open up an administrative level command prompt and type ipconfig /flushdns and hit Enter.
Parameters available is /? (displays usage information), /g (displays the current time zone ID), /s (sets the current time zone using the specified time zone ID, with the _dstoff suffix disables Daylight Saving Time adjustments for the time zone), and /l (lists all valid time zone IDs and display names).
For example:
TZUTIL /g
TZUTIL /s “Pacific Standard Time”
TZUTIL /s “Pacific Standard Time_dstoff”
TZUTIL /s “GMT Standard Time”
The last command will set the PC time zone to Greenwich Meridian Standard Time (GMT or UTC).
Tip: To get a list of available time zone IDs, type TZUTIL /l. – would have been nice in XP!
Disable Software-Distribution:
WMIC /namespace:\rootccmpolicymachinerequestedconfig 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:\rootccmpolicymachinerequestedconfig path ccm_SoftwareDistributionClientConfig WHERE ComponentName=”Disable SWDist” delete /NOINTERACTIVE
Trigger Hardware Inventory:
WMIC /namespace:\rootccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000001}” /NOINTERACTIVE
Trigger Software Inventory:
WMIC /namespace:\rootccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000002}” /NOINTERACTIVE
Trigger DataDiscoverRecord (DDR) update:
WMIC /namespace:\rootccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000003}” /NOINTERACTIVE
Force a FULL HW Inventory on next HW-Inv Schedule:
WMIC /namespace:\rootccminvagt path inventoryActionStatus where InventoryActionID=”{00000000-0000-0000-0000-000000000001}” DELETE /NOINTERACTIVE
Repair SMS/SCCM Agent on a remote client:
WMIC /node:%MACHINE% /namespace:\rootccm path sms_client CALL RepairClient
Repair a list (all clients listed in clients.txt) of remote SMS/SCCM Agents:
WMIC /node:@clients.txt /namespace:\rootccm path sms_client CALL RepairClient