How to change name or description on secondary sites without having to reinstall…..
Keep in mind, this method is NOT supported by Microsoft !
This and other support announcements located here:
Microsoft SQL Server 2008 R2 is now supported on Configuration Manager 2007 SP1 and SP2 and Configuration Manager 2007 R2
System Center Configuration Manager 2007 SP1 and SP2 now support Microsoft SQL Server 2008 R2 as a Configuration Manager 2007 site database. System Center Configuration Manager 2007 R2 now supports Microsoft SQL Server 2008 R2 Reporting Services.
No software updates are required.
Microsoft Application Virtualization 4.5 Service Pack 2 is now supported on Configuration Manager 2007 R2 with Configuration Manager 2007 SP2
System Center Configuration Manager 2007 R2 with System Center Configuration Manager 2007 SP2 now supports Microsoft Application Virtualization 4.5 Service Pack 2.
No software updates are required.
Hyper-V Server 2008 R2 is now supported with Configuration Manager 2007 Service Pack 2.
System Center Configuration Manager 2007 SP2 now supports client installation and all site server roles in the Hyper-V Server 2008 R2 virtualization environment.
No software updates are required.
Microsoft Windows Embedded Standard 7 is now supported on Configuration Manager 2007 SP2
System Center Configuration Manager 2007 SP2 now supports Windows Embedded 2011 as a client platform. General limitations for managing Windows Embedded devices can be found in this article, http://technet.microsoft.com/en-us/library/bb932123.aspx,
No software updates are required.
.NET Framework 4.0 is now supported with Configuration Manager 2007 SP1 and SP2.
System Center Configuration Manager 2007 SP1 and SP2 now support the .NET Framework 4.0 with the following limitations.
HKEY_LOCAL_MACHINESOFTWAREMicrosoft.NETFrameworkOnlyUseLatestCLR
No software updates are required.
Application Compatibility Toolkit 5.6 is now supported with the Application Compatibility Toolkit Connector.
The Application Compatibility Toolkit (ACT) Connector now supports ACT 5.6. Limitations and workarounds for upgrade issues from ACT 5.5 are documented in the following blog post: http://blogs.technet.com/b/configmgrteam/archive/2010/06/20/act-connector-and-act-5-6.aspx
No software updates are required.
Error from WUHandler.log:
Its a WSUS Update Source type ({B4F31904-A2D1-411C-AF25-9C68F7969A31}), adding it.
Existing WUA Managed server was already set (http://<SOMESERVER>:8530), skipping Group Policy registration.
Added Update Source ({B4F31904-A2D1-411C-AF25-9C68F7969A31}) of content type: 2
Async searching of updates using WUAgent started.
Async searching completed.
OnSearchComplete – Failed to end search job. Error = 0x8024401b.
Scan failed with error = 0x8024401b.
Error from WindowsUpdates.log:
1284 804 PT WARNING: GetConfig failure, error = 0x8024401B, soap client error = 10, soap error code = 0, HTTP status code = 407
1284 804 PT WARNING: PTError: 0x8024401b
1284 804 PT WARNING: GetConfig_WithRecovery failed: 0x8024401b
1284 804 PT WARNING: RefreshConfig failed: 0x8024401b
1284 804 PT WARNING: RefreshPTState failed: 0x8024401b
1284 804 PT WARNING: PTError: 0x8024401b
1284 804 Report WARNING: Reporter failed to upload events with hr = 8024401b.
Solution:
And this is wierd!
Change the site system FQDN to lowercase (Site Database -> Site Management -> Central Site -> Site Settings -> Site Systems -> <siteserver> -> ConfigMgr Site System)
Restart the Windows Update Service on the client computer
Initiate the Software Update Scan Cycle and you are go!
When deploying Windows 7 the Network Location dialog box is sometimes shown even though the machine is joined to a domain. It’s only on specific hardware but it’s quite common.
Microsoft now has a hotfix (KB 2028749) for this bug.
A “Set Network Location” dialog box appears when you first log on to a domain-joined Windows 7-based client computer
http://support.microsoft.com/kb/2028749/
Optional Workaround:
You can set a Group Policy for Network Location – Computer Configuration / Windows Settings / Security Settings / Network List Manager Policies / All Networks. Change Network Location to User cannot change location
This is the dialog box you might get without the hotfix…
Checkout PowerCFG…
just a few examples:
Changes plan to “High Performance”
powercfg -s 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c
also works from task sequence – cmd.exe /c “powercfg -s 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c”
just a few exampes:
powercfg /change “always on” /standby-timeout-ac 0
powercfg /change “always on” /hibernate-timeout-ac 0
powercfg /setactive “always on”
Read more at: Using PowerCfg to Evaluate System Energy Efficiency
Solution 1:
Firmware update the DVD drive with latests firmware, maybe it supports Adaptive Link Power Management.
Solution 2:
Just disable the Adaptive Link Power Management ..
Run the following commands:
powercfg.exe -setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 0012ee47-9041-4b5d-9b77-535fba8b1442 DAB60367-53FE-4fbc-
825E-521D069D2456 0
powercfg.exe -setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 0012ee47-9041-4b5d-9b77-535fba8b1442 DAB60367-53FE-4fbc-
825E-521D069D2456 0
powercfg.exe -setacvalueindex 381b4222-f694-41f0-9685-ff5bb260df2e 0012ee47-9041-4b5d-9b77-535fba8b1442 DAB60367-53FE-4fbc-
825E-521D069D2456 0
powercfg.exe -setdcvalueindex 381b4222-f694-41f0-9685-ff5bb260df2e 0012ee47-9041-4b5d-9b77-535fba8b1442 DAB60367-53FE-4fbc-
825E-521D069D2456 0
powercfg.exe -setacvalueindex a1841308-3541-4fab-bc81-f71556f20b4a 0012ee47-9041-4b5d-9b77-535fba8b1442 DAB60367-53FE-4fbc-
825E-521D069D2456 0
powercfg.exe -setdcvalueindex a1841308-3541-4fab-bc81-f71556f20b4a 0012ee47-9041-4b5d-9b77-535fba8b1442 DAB60367-53FE-4fbc-
825E-521D069D2456 0
Following is an overview of the Configuration Manager 2007 support for the different SQL Server versions:
SQL Server 2005:
SQL Server 2008:
After a look at the forums, it seems that Symantec’s virus definitions dated June 21, 2010 r2 have identified various components of the awesome SCCM Right Click Tools (which i personally couldn’t survive without) as “Trojan.Gen” Since this is a generic detection name “for many individual but varied Trojans for which specific definitions have not been created. A generic detection is used because it protects against many Trojans that share similar characteristics” this has to be a false positive. This is just another example of how definition based anti-virus tools are a out dated concept.
Office 2010 will require either a MAK (Multiple Activation Key) or a KMS Key (the new volume lenience key, since Vista/Server 2008). You will only need one KMS server for your organization to serve out activations for both Windows Operating Systems and Office 2010.
| 1. |
Download your Office Product and KMS Key from Microsoft Licensing |
|
|---|---|---|
| 2. |
Download the Microsoft Office 2010 KMS Host License PackDownload this .exe from Microsoft and install it on your current KMS server. It will ask you for your Office 2010 KMS key and then activate it against Microsoft’s Activiation Servers. http://www.microsoft.com/downloads/details.aspx? The Host Service Pack can only be installed on Server 2003, Server 2008 R2 or Volume Licence edition of Windows 7. Once the key has activated you will receive a message indicating that the activation was successful. |
|
| 3. |
Let your clients with Office 2010 activate to the new KMS host keyYou’re all set, your clients should now activate to your KMS server. |
The KMS Host key for Office 2010 is somewhat different than that of the client OS’s, as it will only take 5 users running Office 2010 for the KMS to activate them, as compared to the 25 hosts required for client OS’s.
Also, if a client is off of the network and does not contact the KMS server after 180 days the user will receive a message when they open Office stating that the product is unlicensed, however, it will continue to work with no loss of functionality. Once the user connect to the network with the KMS host the error will go away and the re-activation process will be transparent to the end user.