anyweb

KB974014 - Windows 7 and 2008 R2 support added for SMS 2003 http://support.microsoft.com/kb/974014 We recognize that Windows 7 is an opportunity for organizations to reduce their costs, improve security, and improve productivity. Windows 7 helps achieve these goals. However, organizations do not maximize the return on investment of Windows 7 without modern infrastructure to support it. We want organizations to benefit from the latest platform's features. To achieve these goals, we want to help organizations migrate to our latest management platform. To do this, we have released a compatibility pack that adds Windows 7 and Windows Server 2008 R2 as supported clients in Microsoft Systems Management Server (SMS) 2003 Service Pack 3 (SP3). This compatibility pack helps SMS 2003 SP3 users migrate their software to Configuration Manager 2007 while realizing immediate benefits from their Windows 7 investment. Note This compatibility pack is a one-time offer. We have no plans to offer future compatibility packs to support future versions of Windows on SMS 2003 SP3. This compatibility pack does not provide support for the administrator console, for any site-server roles, for any SMS 2003 feature pack, or for any SMS 2003 add-in. An example of a feature pack is the Operating System Deployment Feature Pack for Windows 7 or for Windows Server 2008 R2. The SMS 2003 Inventory Tool for Microsoft Updates Revision 3 supports software-update deployments to Windows 7 and to Windows Server 2008 R2. General information about ITMU Revision 3 (http://technet.microsoft.com/en-us/sms/bb676783.aspx) We are releasing this compatibility pack to the general public at no cost. The support life cycle for SMS 2003 ended the Mainstream Support phase on January 12, 2010. SMS 2003 nonsecurity hotfixes that are released after January 12, 2010, follow the Microsoft Lifecycle Support policy and require Extended Hotfix Support. General information about the Extended Hotfix Support program (http://www.microsoft.com/microsoftservices/en/us/support_premier_addons_ehs.aspx) Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. To resolve compatibility issues, install this compatibility pack on all site servers that are running SMS 2003 SP3. Compatibility pack information Prerequisites To apply this compatibility pack, your computer must have SMS 2003 SP3 installed. Compatibility issues The following are the compatibility issues that this compatibility pack addresses. Issue 1 The clients that are running Windows Server 2008 R2 or Windows 7 are not listed in the Supported Platforms list for SMS Programs for Software Distribution. Issue 2 The clients that are running Windows Server 2008 R2 or Windows 7 are registered incorrectly when they are discovered by Active Directory System Discovery feature. This issue may affect the Client Push Installation feature or the collections that are created and that rely on the discovery data. How to use the Update.sql file This hotfix contains an Update.sql file. To use the Update.sql file, follow these steps: 1. On the updated SMS site server, stop the following services: * SMS_SITE_COMPONENT_MANAGER * SMS_EXECUTIVE 2. At the SMS site database server, load the following file by using a SQL Server query tool such as Query Analyzer or ISQL/W: <SMS_root>\Logs\<KBID>\Update.sql 3. In the SQL Server query tool, select the Systems Management Server database. 4. Run the script. 5. Restart the following SMS site server services: * SMS_SITE_COMPONENT_MANAGER * SMS_EXECUTIVE File information The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files. Collapse this tableExpand this table File name File version File size Date Time Platform Adsource.dll 2.50.4253.3128 131,072 31-Jul-2007 20:15 x86 Baserc.dll 2.50.4253.3128 61,440 31-Jul-2007 20:15 x86 Update.sql Not Applicable 46,084 31-Jul-2007 20:15 Not Applicable For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: 824684 (http://support.microsoft.com/kb/824684/ ) Description of the standard terminology that is used to describe Microsoft software updates Back to the top APPLIES TO * Microsoft Systems Management Server 2003 Service Pack 3

try accessing the share from the box you are working on, looks like it just cannot connect, check using the NAA (network access account) cheers niall

create the package the same way as i do in this example via an Install Software step in the TS.

as it's XP, its most likely related to your HAL or storage so checkout the SATA settings in the bios and change them to ATA (compatible) cheers niall

could it be this ? Windows Installer Error 1623 This language of this installation package is not supported by your system.

hi all, as this is a common requirement, here are two Task Sequences I use for demoing Windows XP migrations to Windows 7, Related Reading:- OSDMigrateAdditionalCaptureOptions on Technet OSDMigrateAdditionalRestoreOptions on Technet Before you can use these sample task sequences you must have done the following Steps. Using Computer Association add a computer to your Deploy XP collection, and then Deploy Windows XP to that computer. Once Deployed with XP you can use Direct Membership to add that computer to the Migrate XP to 7 Collection described below. XP to Windows 7 Demo - X86 using Hardlinking The first task sequence XP to Windows 7 Demo - X86 using Hardlinking.xml will migrate XP to Windows 7 using hardlinking XP to Windows 7 Demo - X86 using Hardlinking.xml XP to Windows 7 Demo - X86 using SMP The second one uses a SMP *State Migration Point* XP to W7 Demo - X86 using SMP.xml simply import these task sequences into ConfigMgr, and replace the missing package references (configmgr X86 boot images, microsoft deployment 2010 settings, mdt2010 files, windows 7 autologin enable package, usmt4 package and the Windows 7 X86 WIM file itself). See below screenshots to help you with that Task Sequence References with hardlinking Task Sequence References with SMP and then advertise the task sequences to a migrate XP to Windows 7 collection add computers to the Migrate XP to Windows 7 collection and kick off the appropriate TS via RAP.

because it cant find the script to run, create it as a package instead, with a program. and the program shall be the vbs script or cmd file

did you update collection membership and press F5 to refresh ?

i'm lost at your description of the problem, so let's simplify it Dom. are you saying that your TS is failing the three tasks ? if so, which of the three is it failing on ? why do you have a boot image attached to this TS, why is there a reboot ?

did you Add a "Set Task Sequence Variable" to the postinstall phase before the "Apply Windows Settings" step ? see the following screenshot, however in this screenshot i'm making the computername=the Asset Tag of the computer all you have to do is to leave the assettag value empty

maybe office 2007 is being installed to a collection you are in ?

yes this still on target however i'm lacking two things at this point: 1. some software for making Webcasts, any recommendations ? 2. time do do the webcasts cheers niall

Reports have surfaced about a new security hole that has been in Windows since the release of Windows NT 3.1 on July 27, 1993. The vulnerability is present in all 32-bit versions of Windows released since then, including all supported versions: Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, and Windows 7. Microsoft has issued Security Advisory (979682) to address the elevation of privilege vulnerability in the Windows kernel, making sure to note that 64-bit versions of Windows, including Windows Server 2008 R2, are not affected. ... Despite the fact that there is no patch available from Microsoft, Ormandy decided to publish the information because he believes the workaround is simple enough: disable the MS-DOS subsystem. via > http://arstechnica.com/microsoft/news/2010/01/microsoft-investigates-17-year-old-windows-flaw.ars

As promised, Microsoft released the patch that fixes the Google attack vulnerability. Seven other holes are closed off as well. "Microsoft on Thursday issued a cumulative critical patch for Internet Explorer that fixes eight vulnerabilities, including a hole targeted in the China-based attacks on Google and other U.S. companies. The security update is rated critical for all supported releases of IE 5, 6, 7, and 8, according to the advisory. The more severe vulnerabilities could allow remote code execution if a user views a malicious Web page using IE, it said." via > http://www.osnews.com/story/22774/Microsoft_Fixes_8_IE_Holes_Including_One_Used_in_Attacks

well lots of ways but most commonly discovery methods as they are what puts your computer or user in a collection in the first place (unless you add them using direct membership queries or such like), and you are most likely basing your application installs on what collection a user/computer is a member of, so... you could tweak your discovery methods to go more often, and for the collection update to update itself within a time period that corresponds to the discovery methods so lets say you do some AD discoverys every 3 hours, well then you might want some application collections refreshing themselves every 4 hours, I would strongly suggest testing this backwards in a lab, here are some good pointers Deploy software through AD Groups linked to Collections in SCCM, AD Group for deployments everyone needs software eventually Fully automated Application Groups One of the best ways of using AD groups for deploying software in addition to the above, the user (and computer if used) policy updates on the CLIENT will need to be tweaked cheers

hi Matt a simple alternative would be to have a thick image (your base os plus vital apps like office, adobe reader, winzip, whatever...) and let the other less commonly used apps install as normal via SCCM let's see what the others have to say about it cheers niall

it's this

i think proxy settings have to be configured via the Internet Explorer Administration Kit, have you checked that out ? of course if you find out differently post it here

can't you increase the hdd size/partition size/storage of the vm ?

Posted by Ed Bott @ 12:05 pm I just spoke with George Stathakopoulos, General Manager of Trustworthy Computing Security at Microsoft, regarding the ongoing security issue affecting Internet Explorer. (For background, see my earlier post, It’s time to stop using IE6. For an update on the vulnerability and its impact, see this Zero Day blog post from ZDNet’s Ryan Naraine.) According to Stathakopoulos, a security update for all versions of Internet Explorer will be released “out of band” - that is, earlier than the next regularly scheduled update cycle on Patch Tuesday, February 9. The update is currently undergoing testing, and Microsoft expects to announce a release schedule tomorrow, January 19. Separately, Gregg Keizer at ComputerWorld reports that French security researchers claim to have circumvented the Data Execution Prevention security feature and executed their own exploit code on Internet Explorer 8 with DEP enabled. A Microsoft spokesperson says they are investigating those claims and “will take appropriate action to help protect customers.” Stathakopoulos reiterated that Microsoft so far has seen only “very limited and targeted attacks” and confirmed that the only successful attacks have been against IE6. via > http://blogs.zdnet.com/Bott/?p=1651

if you reinstall sp2 on this box does it change the version of the boot image ?

sorry, i meant the Windows PE tab, it lists the drivers

if you click on the drivers tab of that boot image are any listed ?

well the sp2 update wont update custom images, the boot images (both those that get updated and those that fail to update) are listed in the ConfigMgrSetup.log

can you show a screenshot(s) of what you did so others will know ? cheers niall