anyweb

Microsoft's beta release of its Windows Phone 7 Development Training Kit offers several new labs designed to let developers get their feet wet in the new platform. Described Tuesday in a Microsoft blog, the new beta of the training kit keeps up with the changes found in the Windows Phone 7 Developer Tools, which also hit beta status this week. Microsoft has revamped the existing labs in the training kit and added a few new ones. The lab dubbed "Using Windows Phone Launcher and Choosers In Your Applications" exposes the APIs that developers can tap into when writing their apps to run common tasks, such as making phone calls, sending e-mail, and snapping photos. The lab called "Understanding the Windows Phone Application Lifecycle (handling Tombstone)" delves into "tombstoning," or what happens when when a person navigates away from an app and the OS thus ends the app's process--a necessary task since Windows Phone 7 does not support application multitasking. The new labs include "Hello Phone," a variation of the familiar "Hello World" program that developers create when learning a new programming language. This lab helps developers learn to use Microsoft Visual Studio 2010 Express for Windows Phones and Expression Blend to build their apps, according to Microsoft. The lab on "Building Your First Windows Phone Application" presents a puzzle game designed to take developers on a tour of the different stages of creating an app. The "Windows Phone Navigation and Controls" explains how to navigate among the different screens in a Windows Phone Silverlight app. And the "Game Development with XNA Framework for Windows Phone" teaches developers how to create a basic XNA game app for the phone. Interested developers can download the training kit to install it locally or use the online edition at Microsoft's Channel 9 Web site to view session videos. via http://news.cnet.com/8301-10805_3-20010526-75.html

interesting points and yes your search folders will produce different results based on your criteria, experimenting will give you a better overview, as regards not including certain updates (patches) from your statement correct, by including MS as the bulletin ID (or MS10 or whatever) we are looking for Security Updates only , only SEcurity Updates are given a bulletin ID. if you want All Security Updates AND all other updates, create another search folder called 'all updates' for the given OS and do not include bulletin ID as a search category, see the difference ?

you'll need to configure an SLP if you don't extend AD, see here for more info http://technet.microsoft.com/en-us/library/bb693467.aspx

not an issue, just install the SCCM admin console on your windows 7 or windows xp desktop and create the key there, works fine !

i'm not following your question, what exactly is the problem you have ?

are you using sccm 2007 r2 ? if so you can utilise the unknown computer collection in the R2 feature pack, alternatively if you dont, did you add your computer to the deployment colleciton you created below ?

Please Note: This early release of Windows 7 and Windows Server 2008 R2 SP1 Beta is not available for home users. The SP1 Beta does not provide new end-user features, and installation is not supported by Microsoft. Windows 7 and Windows Server 2008 R2 SP1 Beta helps keep your PCs and servers on the latest support level, provides ongoing improvements to the Windows Operating System (OS), by including previous updates delivered over Windows Update as well as continuing incremental updates to the Windows 7 and Windows Server 2008 R2 platforms based on customer and partner feedback, and is easy for organizations to deploy a single set of updates. Windows 7 and Windows Server 2008 R2 SP1 Beta will help you: * Keep your PCs supported and up-to-date * Get ongoing updates to the Windows 7 platform * Easily deploy cumulative updates at a single time * Meet your users' demands for greater business mobility * Provide a comprehensive set of virtualization innovations * Provide an easier Service Pack deployment model for better IT efficiency In order to download and install the Windows 7 and Windows Server 2008 R2 SP1 Beta you must currently have a Release to Manufacturing (RTM) version of Windows 7 and Windows Server 2008 R2 already installed. To learn more about piloting, deploying and managing Windows 7, visit the Springboard Series on TechNet. To learn more about SP1 Beta and Windows Server 2008 R2, visit the SP1 Details Page. Register for Download and Guided Evaluation Review Windows 7* and Windows Server 2008 R2 system requirements and the frequently asked questions (FAQ) Register for evaluation Download and install beta software Receive an email with resources to guide you Question on the beta? Please visit the Windows Support Forum or the Windows Server 2008 R2 Migration & Deployment Forum for additional guidance *Windows 7 Minimum System Requirements: * 1 GHz or faster 32-bit (x86) or 64-bit (x64) processor * 1 GB of RAM (32-bit) / 2 GB RAM (64-bit) * 16 GB available disk space (32-bit) / 20 GB (64-bit) * DirectX 9 graphics processor with WDDM 1.0 or higher driver * DVD-compatible drive * Internet access (fees may apply) Note: Some product features of Windows 7, such as the ability to watch and record live TV, BitLocker, or navigation through the use of “touch,” may require advanced or additional hardware. Windows XP Mode requires an additional 1 GB of RAM and 15 GB of available disk space. Download using Windows Update for the 32-bit or 64-bit versions or download the ISO which contains both 32-bit and 64-bit versions for Windows 7 and Windows Server 2008 R2. Check the FAQ for which version you should download. Register for the Download http://technet.microsoft.com/en-us/evalcenter/ff183870.aspx

Just a day before Microsoft drops support for Windows XP Service Pack 2 (SP2), the company has announced that people running some versions of Windows 7 can "downgrade" to the aged operating system for up to 10 years. The move is highly unusual. In the past, Microsoft has terminated downgrade rights - which let customers replace a newer version of Windows with an older edition without paying for two copies - within months of introducing a new OS. While few consumers may want to downgrade from Windows 7 to XP - unlike when many mutinied against Vista three years ago - businesses often want to standardise on a single operating system to simplify machine management. Monday's announcement was the second Windows XP downgrade rights extension. Microsoft originally limited Windows 7-to-Windows XP downgrades to six months after Windows 7's release, but backtracked in June 2009 after an analyst with Gartner Research called the plan a "real mess." Instead, Microsoft later said it would allow downgrades to Windows XP until 18 months after the October 2009 debut of Windows 7, or until it released Windows 7 SP1. In either scenario, XP downgrade rights would have expired sometime in 2011, perhaps as early as April. On Monday, Microsoft again changed its mind. Users running Windows 7 Professional or Ultimate will now be able to downgrade to Windows XP Professional throughout the entire lifecycle of Windows 7. "Our business customers have told us that the removing end-user downgrade rights to Windows XP Professional could be confusing," said Microsoft spokesman Brandon LeBlanc, in an entry on the a company blog. Windows 7 Professional won't be fully retired until January 2020; the Ultimate edition will be put out to pasture five years earlier, in January 2015. Although Microsoft said it made the change to simplify the work in tracking licensing rights for PCs, the continued popularity of Windows XP may have had something to do with it. At the Worldwide Partner Conference (WPC), which opened Monday in Washington DC, a company executive acknowledged that 74% of business computers still run XP. The downgrade rights are available only from OEM copies of Windows 7, those that are pre-installed by computer makers. "Going forward, businesses can continue to purchase new PCs and utilise end-user downgrade rights to Windows XP or Windows Vista until they are ready to use Windows 7," LeBlanc added in his blog post. The change impacts only consumers and businesses that don't subscribe to Software Assurance (SA) - Microsoft's annuity-like upgrade guarantee programme - or those who purchase Windows through volume-licensing plans. Those companies already had downgrade rights from any edition, including Windows 7, to any previous version going as far back as Windows 95. Other deadlines that Microsoft had previously scheduled for Windows remain in place. Computer manufacturers must stop installing Windows XP Home on netbooks as of October 22, 2010, and they may sell PCs with Vista pre-installed only through October 22, 2011. Computer makers are also scheduled to stop offering factory-installs of XP Professional downgrades on PCs with Windows 7 Professional licences after October 22, 2010. That means Windows users who want to downgrade a Windows 7 system to XP must do it themselves starting October 23 of this year. It's unlikely that many Microsoft customers, even the largest corporations, will downgrade to XP as long as Microsoft allows. That's because the nearly-nine-year-old operating system falls off the support list for good in April 2014. Today, Microsoft will supply the last-ever updates for Windows XP Service Pack 2 (SP2), the 2004 upgrade that was superseded four years later by XP SP3. However, some computer makers continue to sell new PCs with a factory-installed downgrade to Windows XP. Dell , for example, offers downgrades on some Latitude notebooks. The practice was much more widespread when Microsoft marketed Windows Vista. Then, customers clamored for ways to return to XP after buying new PCs equipped with Vista, a rebellion that forced Microsoft to delay several times the end of XP availability to both large and smaller computer sellers. via > http://www.pcadvisor.co.uk/news/index.cfm?newsid=3230557

this post shows you how to set it up (wsus/sup/sccm), the collection that you need to advertise the deployment management task to is the Unknown Computers collection, think about it

do you just want to deploy a boot image (winpe) or an entire os ?

what dell switches are these ?

to add to peters answer, create a deployment management task in the software updates section of ConfigMgr, and point that task collection tab to the collection that your computer is in during deployment, typically the Unknown Computer collection

verify that the machine isnt simply marked obsolete, take a look at the abortpxe thread here and you'll see what i mean, sccm can't be learnt quickly, it takes time to master, and you must be patient with it, also, what may have appeared simple in altiris can indeed be different or even hard in SCCM, you'll understand it soon enough, but you have to be patient as regards not being able to pxe boot over and over, that is by design, what environment would you want to reimage computers over and over in the same day ? it's perfectly possible with SCCM but you need to understand how it all works first. take a look at the smspxe.log file and look at the wds registry key (cache) by default with sp2 it's 60 mins of wait time.... before allowing you to reimage a box

if any of you are interested here's a quick overview of the site stats over the last year, thankfully the graph is going in the right direction ! in fact, it's July 10th and already we have more than double page views than August one year ago take a look if you want more detail just ask cheers niall

and thanks for sharing, i guessed it was proxy related sorry for the late reply but glad it's sorted now

yes there is and if you take a look at the deploy 7/deploy xp/vista/windows server 2008 guides you'll see that i separate production from lab for this exact scenario here's a sample of what i mean, scroll to the Schedule section

what os and what version of configmgr client ?

well there are a number of ways of doing this, did you try to right click on the computer and clear last PXE ?, is the program rerun behaviour set to rerun if failed or never rerun ?

Imagine the scenario, you deploy some Windows 7 laptops but receive feedback from the users that they don't like the power management default settings, to get around this you could use Group Policy or if that's not possible due to time constraints or other issues, you could import the power management settings directly into your image based on whether the target pc is a Laptop or Desktop. The default power management plans in Windows 7 are pretty good, but also quite aggressive, so you will probably want to configure them in some way, View current PowerScheme First of all you will need to understand how to 'see' them. On a Client Laptop (not a VM or desktop, as they won't show the profiles we are interested in) open a administrator command prompt and type powercfg -list from the above we can see the the Balanced power plan is selected currently. Export current PowerScheme Now let's make some changes to our Power scheme (as a test, change the values for hard disc time out in advanced properties of the current plan). Once you have power management the way you want, we will export our settings using powercfg -export Import a previously exported PowerScheme Now that we have our pow settings saved, let's import them (on another computer) using powercfg -import and verify Note that even though the scheme is imported, it's not set as default, to do that we have to use the powercfg -set command. Set current PowerScheme Ok now that we know how to import it, let's set a powerscheme, to do so use powercfg -setactive guid let's verify the change It Worked and now our powerscheme is set to our custom scheme.

hi Johan sorry for the delay in replying, have you checked your timezone settings ?

Are you running a 64-bit edition of Windows 7? There is a high likelihood you are. As of June 2010, we see that 46% of all PCs worldwide running Windows 7 are running a 64-bit edition of Windows 7. That is, nearly half of all PCs running Windows 7 are running 64-bit. Compared to Windows Vista at 3 and a half years after launch, only 11% of PCs running Windows Vista worldwide are running 64-bit. With Windows 7, running a 64-bit OS is becoming the norm. A primary benefit of 64-bit Windows is the increase in addressable memory. This makes more “bits” available to Windows (the OS), which means more information can be “addressed” at once. 32-bit architectures have a memory ceiling of 4GB while the 64-bit architecture increases the memory ceiling to approximately 17.2 billion GB or RAM! Windows 7 is designed to use up to 192 GB of RAM (see SKU and OS comparisons here), a huge jump compared to limits with all 32-bit systems. Essentially, 64-bit Windows allows your PC to take advantage of more memory to do more things. If you are like me and are running tons of apps, you can see a real difference in performance. Aside from the performance gains, there are also security enhancements and support for virtualization as well. The reason for the jump in transition to 64-bit PCs can be attributed to a few things. The first is the price of memory has dropped over the last several years making it easier for OEMs to up the amount of memory in the PCs they ship. And most major processors in PCs today are capable of running a 64-bit OS. There are also more and more compatible devices and applications for PCs running 64-bit Windows 7– but I’ll talk more about this in a minute. OEMs today have fully embraced 64-bit. We have seen many OEMs convert entire consumer lines of PCs to 64-bit only – which can be seen quite a bit today in North America. According to Stephen Baker at NPD, 77% of PCs sold at retail in April 2010 in the U.S. had a 64-bit edition of Windows 7 pre-installed. And businesses are adopting Windows 7 64-bit as well. According to Gartner*, by 2014 75% of all business PCs will be running a 64-bit edition of Windows. Intel recently migrated to 64-bit Windows 7 citing the following on their deployment: “Our decision to move to 64-bit computing allows us to take advantage of new systems with higher memory capabilities while positioning Intel to take advantage of 64-bit applications as they become available. Moving to this computing model also provides additional security benefits, including Data Execution Prevention (DEP), which helps prevent malicious code exploits by disallowing applications from executing code from a non-executable memory region.” Intel has released a whitepaper on their deployment of 64-bit Windows 7, which can be found here. As I mentioned previously, there are more compatible hardware and software for PCs today thanks to the amazing work from our partners (ISVs and IHVs) making their products compatible with 64-bit. Through the Windows Logo Program (the “Compatible with Windows 7” logo today), hardware partners are required to develop 64-bit drivers for their devices and software partners are required to have their applications compatible with 64-bit Windows 7. This groundwork was laid with the Windows Logo Program for Windows Vista and carries through to today with Windows 7. To understand more about hardware and software for 64-bit Windows, check out this article by our Help and How-to team. To find out what’s compatible with 64-bit Windows 7, millions of consumers and businesses are visiting the Windows 7 Compatibility Center where they can easily check 64-bit compatibility on thousands of devices and applications, get 64-bit driver and software downloads and send feedback on their experience. You can also find products that have met the Windows testing requirements to earn the “Compatible with Windows 7” logo. And the Windows 7 Compatibility Center recently went international with support for 17 markets in 12 languages - see this recent post by Mark Relph on the latest release. To find out if your PC can run a 64-bit edition of Windows 7, you can run the Windows 7 Upgrade Advisor. If your PC isn’t currently capable of running a 64-bit edition of Windows 7, the Windows 7 Upgrade Advisor will let you know if there are any memory upgrades that might be done to move to 64-bit. If you buy a new PC, you are likely to get 64-bit Windows 7 pre-installed but if you decide to upgrade your PC, all versions of Windows 7 (except Starter) include both a 32-bit and 64-bit DVD in the box. As you can see, millions of consumers and business customers alike are making the transition to 64-bit computing with Windows 7. For me personally, almost every laptop and desktop PC I have is running 64-bit Windows 7. Happy 64-bit computing! * Gartner, Inc., “Plan to Implement Some 64-Bit Versions of Windows 7,” Stephen Kleynhans, October 6, 2009 via > http://windowsteamblog.com/windows/b/bloggingwindows/archive/2010/07/08/64-bit-momentum-surges-with-windows-7.aspx

Deploy Windows 7 and Office 2010 quickly and reliably—while boosting user satisfaction Microsoft® Deployment Toolkit (MDT) 2010 Update 1 is now available! Download MDT 2010 Update 1 at: http://go.microsoft.com/fwlink/?LinkId=159061 As you prepare to deploy Windows® 7, Office 2010, and Windows Server® 2008 R2, get a jump start with MDT 2010 Update 1. Use this Solution Accelerator to achieve efficient, cost-effective deployment of Windows 7, Office 2010, and Windows Server 2008 R2. This latest release offers something for everyone. Benefits include: For System Center Configuration Manager 2007 customers: New “User Driven Installation” deployment method. An easy-to-use UDI Wizard allows users to initiate and customize operating system and application deployments to their PCs that are tailored to their individual needs. Support for Configuration Manager R3 “Prestaged Media.” For those deploying Windows 7 and Office 2010 along with new PCs, a custom operating system image can easily be preloaded and then customized once deployed. For Lite Touch Installation: Support for Office 2010. Easily configure Office 2010 installation and deployment settings through the Deployment Workbench and integration with the Office Customization Tool. Improved driver import process. All drivers are inspected during the import process to accurately determine what platforms they really support, avoiding common inaccuracies that can cause deployment issues. For all existing customers: A smooth and simple upgrade process. Installing MDT 2010 Update 1 will preserve your existing MDT configuration, with simple wizards to upgrade existing deployment shares and Configuration Manager installations. Many small enhancements and bug fixes. Made in direct response to feedback received from customers and partners all around the world, MDT 2010 Update 1 is an indispensible upgrade for those currently using MDT (as well as a great starting point for those just starting). Continued support for older products. MDT 2010 Update 1 still supports deployment of Windows XP, Windows Server 2003, Windows Vista®, Windows Server 2008, and Office 2007, for those customers who need to be able to support these products during the deployment of Windows 7 and Office 2010. Next steps: Download Microsoft Deployment Toolkit 2010: http://go.microsoft.com/fwlink/?LinkId=159061. Learn more by visiting the MDT site on Microsoft TechNet: www.microsoft.com/mdt. Get the latest news by visiting the Microsoft Deployment Toolkit Team blog: http://blogs.technet.com/msdeployment/default.aspx. Provide us with feedback at satfdbk@microsoft.com. If you have used a Solution Accelerator within your organization, please share your experience with us by completing this short survey: http://go.microsoft.com/fwlink/?LinkID=132579. Sincerely, Microsoft Deployment Toolkit Team ------------------------------------------------------------------------- Microsoft respects your privacy. Please read our online Privacy Statement. You are receiving this email because you are a participant in a Microsoft Connect beta program. You can end your participation in a program at any time by visiting Your Dashboard (http://connect.microsoft.com/dashboard/) page and choosing 'quit' for that program. If you have signed up to be contacted about participating in new Microsoft Connect programs, surveys, and events, you will continue to receive those communications unless you unsubscribe by going to Your Profile (http://connect.microsoft.com/profile.aspx). To set your contact preferences for other Microsoft communications, see the communications preferences section of the Microsoft Privacy Statement. Alternatively, if you would prefer to no longer to be contacted by Microsoft Connect, send an email to mchelp@microsoft.com with 'UNSUBSCRIBE' in the subject line and we will unregister from Microsoft Connect all up. This is an unmonitored e-mail address, so do not reply to this message. Microsoft Corporation One Microsoft Way Redmond, WA 98052

you can download a SMP sample task sequence here - http://www.windows-noob.com/forums/index.php?/topic/1633-sample-xp-to-windows-7-task-sequences

When running the System Center Configuration Manager 2007 client agent on a Windows Server 2003 based computer you may notice one or more of the following symptoms: · Task Manager does not open. · Windows Explorer becomes unresponsive. · The computer stops responding to new RDP connection attempts · Existing RDP sessions hang or time out. When this problem occurs you may have to wait for some time for the server to become responsive again. This problem can occur when CCMEXEC (SCCM Inventory Process) performs a NtQueryDirectoryFile call to scan or query the contents of folders containing more than 20,000 files. For all the latest information and the current recommended workaround see the following Knowledge Base article: KB2248865 - A Configuration Manager 2007 client computer may become unresponsive when scanning folders containing thousands of files J.C. Hornbeck | System Center Knowledge Engineer http://blogs.technet.com/b/configurationmgr/archive/2010/07/07/new-configmgr-2007-kb-a-configuration-manager-2007-client-computer-may-become-unresponsive-when-scanning-folders-containing-thousands-of-files.aspx