Microsoft Office 2013 (Office 15.0) is now available for consumers !!

For download, click HERE and for MSDN members HERE

Languages pack and others download http://search.microsoft.com/en-us/DownloadResults.aspx?q=office%202013&ftapplicableproducts=^Office

Deployment guide for Office 2013 Preview download : http://download.microsoft.com/download/4/8/B/48B0E72E-11C0-4E6E-AA23-6B777FADCF7A/Deployment-guide-for-Office-2013-Preview.pdf

To read more about System Requirements ,visit http://technet.microsoft.com/en-us/library/ee624351(office.15).aspx

Original post, please read http://www.system-center.fr/?p=3240

Listing the comparison between Configuration manager 2007 what we know and configuration manager 2012.

Configuration Manager 2012 RC2 native 64-bit applications no more supported on 32 Bit (OS and Hardware should be 64 Bit).

Site server and Site roles :

Windows Server 2008 (64-Bit)
Windows Server 2008 R2 (64-Bit)
Database (Below are listed for SCCM 2012 RC2):

Supported versions of SQL Server 2008(64-Bit) for RC2:

SQL Server 2008 SP2 Standard and Enterprise with CU7
SQL Server 2008 R2 SP1 and CU4
SQL Server Express 2008 R2 and CU4
If you are running SQL 2008 SP2, install CU7 from http://support.microsoft.com/kb/2617148
If you are running SQL Server 2008 R2 SP1, use CU4 from http://support.microsoft.com/kb/2633146

Distribution Point :

Windows server 2003 (including 32-bit)
windows Vista SP2 and Later (including 32-Bit)

ConfigMgr client :

windows XP SP2 & SP3 (32-Bit and 64-Bit)
Windows server 2003 SP2 (32-Bit and 64-Bit)
vista SP2 (32-Bit and 64-Bit)
Windows 7 TRM And SP1 (32-Bit and 64-Bit)
Windows 2008 SP2 (32-Bit and 64-Bit)
Windows 2008 R2 RTM and SP1 (64-bit)

Admin Console:

Vista SP2 (32-Bit and 64-Bit)
Widows 7 TRN and SP1 (32-Bit and 64-Bit)
Windows 7 SP1 (32-Bit and 64-Bit)
windows 2008 SP2 (32-Bit and 64-Bit)
windows 2008 R2 RTM & SP1 (64-bit)

For more information about Supported Configurations for Configuration Manager,please refer

http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigSiteSystemReq

The above all details are captured from Wally Mead session.

Additional Resources

• Getting Started with System Center 2012 Configuration Manager
• Introduction to Software Updates in Configuration Manager
• Configuring Software Updates in Configuration Manager
• What’s New in Configuration Manager

The Configuration Manager Team is pleased to announce the release of the International version of Configuration Manger 2012 RC1!  It is now available on Connect:
https://connect.microsoft.com/ConfigurationManagervnext/Downloads/DownloadDetails.aspx?DownloadID=39749
 
If you are interested in testing Simplified Chinese or German please install the International build of Configuration Manger 2012 RC1. Be sure to install the same languages on your CAS and all primary sites.
 
We look forward to your feedback for RC1! Please submit your feedback regularly using the TAP Feedback Form (https://connect.microsoft.com/ConfigurationManagervnext/feedback/CreateFeedbackForm.aspx?FeedbackFormConfigurationID=4213&FeedbackType=1).  
 
Thank you,
Configuration Manager TAP Team

The Microsoft Enterprise Desktop Virtualization v2 Beta Refresh is now available for download on the Microsoft Connect site. The updated software provides fixes to customer reported issues and new features including Workspace packager updates which add additional options for customizing the MED-V computer names.

NOTE:  The MED-V_HostAgent_setup.exe replaces the MED-V client install MSI and the MED-V_WorkspacePackager_setup.exe replaces the MED-V console install MSI.   This change simplifies the install and deployment of these components as they now detect install the correct architecture in a single install.  All of the command line options provided for the MSI’s in the previous installs are still supported for these installers.”

The Guest Agent MSI no longer has to be installed by the administrator on the Windows XP image. The Guest Agent is now installed automatically as part of first time setup. For more information see the MED-V Release Candidate Release Notes.

Please read the release notes for important information about upgrading and the rename of the MED-V Installers.

 Release Candidate Release Notes 

 https://connect.microsoft.com/medv/content/content.aspx?ContentID=23311

Download Release Candidate software  :

http://connect.microsoft.com/medv/Downloads/DownloadDetails.aspx?DownloadID=32936

Seen Lot of questions/helps in many forums on the SCCM client issues like client is not reported to SCCM console ,site code unsuccessful, Client is installed but Console shows NO and many more.

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 .
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.

4.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 you can post comment if anything missed from above steps.

Here is the simple script which can be set your computer information as your desktop wall paper .

Download the file from http://technet.microsoft.com/en-us/sysinternals/bb897557.aspx to c:\BGInfo(in mycase it is).Extract and doubleclick on Bginfo.exe.Once you open ,you will see a lot of features on your computer which should displayed to onto computer.so select the required fields and delete remaining and go to File—>click on save as bginfo1.bgi on to c:\BGInfo.

Now create a batch script called bginfo.cmd with the following command lines.

@echo off
Title Sets the computer information as desktop background
c:\BGInfo\BGInfo.exe c:\BGInfo\bginfo1.bgi /timer:0 /accepteula

once this is done,execute the batch script which you have created now and you should be able to see the desktop wall paper like below and this can be applied to computers as Group policy even.

Below is the script to change your desktop wallpaper. You just need to modify the script to point to the location where the ‘wallpaper is located.

You can then include this script in your Domain’s Group Policy’s login or startup script.

‘ —————————-Script to change Desktop Wallpaper—————————————–

dim wshShell
dim sUserName

Set wshShell = WScript.CreateObject("WScript.Shell")
sUserName = wshShell.ExpandEnvironmentStrings("%USERNAME%")

Set oShell = CreateObject("WScript.Shell")
Set oFSO = CreateObject("Scripting.FileSystemObject")

sWinDir = oFSO.GetSpecialFolder(0)
sWallPaper = "C:\Users\eskonr\Pictures\Nice-Windows-7.jpg"

‘ update in registry
oShell.RegWrite "HKCU\Control Panel\Desktop\Wallpaper", sWallPaper

‘ let the system know about the change
oShell.Run "%windir%\System32\RUNDLL32.EXE user32.dll,UpdatePerUserSystemParameters", 1, True

msgbox "done"

You will have to change the bold letter (image path) with your image file path.

Just want to show you how you can enable Language bar at welcome screen in windows 7 at the left corner topside.

Log into your windows 7 computer 1) Go to control panel ,click on Region and Language shown below with screen shots.

Once you have done the all above changes ,Log off the computer. Next time,when you login ,you should be able to see Language bar on the left side top corner to select which Language.

Issue:  

 Client PC’s would not communicate to WSUS 3.0 SP1

 Solution:

 1. Delete the PC from the WSUS console (Client PC’s – The PC will likely have a red X)

 2. At the client PC – Select Start – Run – type CMD

 3. At the command prompt type net stop wuauserv

 4. Navigate to the Windows Directory

 5. Delete the ‘Software Distribution’ Folder

 6. Run Microsoft Update from the Start menu (This will ensure the update software is up to date)

 7. Restart the PC

 8. Select Start – Run – type in the run box http://WSUSServerName/iuident.cab (wsus server name is the name of your server)

 9. You should be prompted to download or open iuident.cab. This confirms network connectivity.

 10. Select Start – Run

 11. type in the run dialog box wuauclt.exe /resetauthorization /detectnow

 12. Wait 10 minuites +/-. The PC should connect to WSUS and begin downloading updates.