anyweb

Based on all the user feedback ignited by the Windows 7 beta, Microsoft has made a set of tweaks to the release candidate of Windows 7. The Engineering 7 weblog details 36 of those tweaks, in quite some detail actually. Let's take a look at some interesting ones. The Aero Peek feature has been received quite positively, as it really can be quite useful when working with lots and lots of windows. It reminds me a lot of Expose - not in how it works, but in how useful it is. When I first heard about Expose, my reaction was "meh". It felt like useless eye candy for Apple Store owners. However, as soon as you started using Expose, it became clear it's a massively useful feature, and I still consider it one of the best additions to window management since, like, forever. Aero Peek falls in the same category: looks gimmicky at first, but once you're used to it, you don't want to live without it. In the RC a much-requested addition has been made: Aero Peek can now also be triggered by the alt+tab switcher. Another addition that really makes me happy (and I'm sure lots of other users as well), is the ability to drag/drop a file on a task bar item and have it open the dropped file in the program you dropped it on. For instance, if you have Notepad pinned to your taskbar, and you drop a html file on it, it will open that file in Notepad. This behaviour is not default, however; you need to press shift as a modifier. Still, a very welcome addition, as it allows for an easy way to open fiels with non-default applications. full story > http://www.osnews.com/story/21050/Microsof...s_7_Beta_and_RC

It's been nearly two months since the beta of Windows 7 was officially released to the general public, and some of us have been getting fidgety to know just what bugs have been reported and what will be fixed. Microsoft was biding its time, letting the information collect and nearly stagnate, when we finally got official word on some of the results of the testing process. The reason it took so long, so says Steven Sinofsky, senior vice president for Windows and Windows Live Engineering Group at Microsoft, is from the sheer feedback, and apparently not just from the Send Feedback option on every Windows 7 program title bar. What we can say for certain, is that we are listening to each and every comment, blog post, news story, MS Connect report, Send Feedback item, and of course all the data and telemetry. So if you want to get a word in to Microsoft, don't shoot an email. They won't read it. Instead write a blog post including the term "Windows 7," and you'll be set. full story > http://www.osnews.com/story/21052/Windows_...d_You_Found_One

had another few today 1. very simple fix, just create the X86 Windows PE boot environment for SCCM boot image and create a new DP and update the DP, in other words, make sure your server has BOTH X64 and X86 boot images even if you are only deploying X64 computers... 2. Contacting Server (xxx.xxx.xxx.xxx) ..... the dots go on for ever and your SMSPXE.log will say things like Device has been accepted but nothing else to give you a clue as to what is actually wrong, the solution in my case was to reset the PASSWORD in AD users and computers for the user i specified in the MDT VBS filter (SMSinstall) once done, error gone cheers anyweb

ok thanks, next time try to remove those watermarks, i fully appreciate the time and effort you obviously put in to do this but no one needs the watermarks, we know you did it, and thats enough, i'll even link your site here ok ? anyway, in my experience with HyperV recently I noticed that when I powered down a two month old virtual machine with many snapshots that it said 'merging 1%'.... and this is not documented anywhere that i could find, long story short, let it merge, it will merge the snapshots and make your vhd a bigger file, if you want to make a backup copy of your vhd *like i did* then do this * take a snapshot just before you power down the virtual machine. * let the merge complete to 100% * copy/backup the contents of your vhd folder to somewhere safe cheers anyweb

nice !

A Microsoft spokesperson confirmed to Betanews this afternoon that the first release candidates (without numerals) for Service Pack 2 for both Windows Vista and Windows Server 2008 will be released to the general public for testing next week. This after private testers with the MSDN and TechNet services receive their copies first. more > http://osnews.com/story/21040/SP2_RC_for_V...oming_Next_Week

the best way is to completey uninstall wsus and reinstall cheers anyweb

anything inside that System Management container ?

check two things, 1. that your SCCM boundary is correctly set and 2. that you have properly setup the System Management container in AD verify both please cheers anyweb

have a quick read of this post to see how to find it

i'm seeing the same thing, i believe that it's acting as expected what are you hoping to do ?

thanks Mike and good luck with implementing it, please let us know how it goes and also feel free to contribute new matter as you learn cheers anyweb

There have been so many dates flying around concerning the upcoming Release Candidate for Windows 7, and it's beginning to become a daily subject in the blogosphere. Just when you thought that we were going to see a Windows 7 RC by the end of February, a trusted source within Microsoft has informed Neowin that the RC will not be ready by the end of February. At this time, Windows 7 RC is internally being tested and the official release date is set for April 10, 2009. The Windows team is right on schedule with development, and if there are no significant problems over the next few weeks the April 10, 2009 release date will remain in tact. Not much information is available at this time. We're uncertain if the release will be a world-wide, and Microsoft is expected to do more testing before releasing a RC build to the public. With that in mind, TechNet and MSDN subscribers should be the first to receive the RC build. A recent email conversation between Paul, over at GeekSmack, and Steven Sinofsky, Microsoft Senior Vice President of Windows, revealed that there have been over 500,000 suggestions since the public launch of the Windows 7 Beta. full story > http://www.neowin.net/news/main/09/02/20/e...april-10th-2009

can you post your smsts.log file here please sounds like it cannot find a policy which might mean you forgot to distribute something to a DP

nope, what version of SQL did you install ?

there are two ways of creating the files right click on updates listed in your search folders and choose DEPLOY or DOWNLOAD either way will 'provision' the updates locally, and the provisioning process is basically making a copy of said files within the SCCM hierarchy, note that if your permissions are ok that it may take some time for the WSUS server to actually download the updates to make them available for use to sccm, in other words, if wsus hasnt downloaded them yet then they cannot be provisioned cheers anyweb

what do the logfiles on the site servers that are failing say..

sounds like share permissions problem, have you resolved this ?

hi that field is just for informing users of what they might need to do before trying to run a program. below is from SCCMs help Program Name Properties: Requirements Tab Additional requirements Specifies any additional requirement information for clients, up to 127 characters. For example, you can notify users that they should shut down all other applications before running the program. This field is optional. If specified, the text appears on client computers in Run Advertised Programs in Control Panel. so you can safely ignore it... cheers anyweb

have you tried running a command line via the task sequence ?

what did you search for in the description field, it's quite fussy show me a screenshot and i'll tell you where youa re going wrong

you say the infrastructure is changing, but will any of the current SCCM setup remain ?

have a look at this post (which got lost when i lost two days data recently.... but I found the post again using googles cache

did you read this yet ? i've moved your post to the correct area within SCCM

here's what microsoft say on the subject http://technet.microsoft.com/en-us/library/cc770832.aspx Prestaging Client Computers Creating Computer Account Objects in AD DS You can use Windows Deployment Services to link physical computers to computer account objects in Active Directory Domain Servers (AD DS). This is called prestaging the client. Prestaged clients are also called known computers. This allows you to then configure properties on the computer account to control the installation for the client. For example, you can configure the network boot program and the unattend file that the client should receive, as well as the server from which the client should download the network boot program. You can create a computer account object and associate it with a physical computer using the following methods: * Using WDSUTIL. You can prestage client computers before they have attempted a network boot, by running WDSUTIL /Add-Device /Device:<name> /ID:<ID>. You cannot prestage computers by using the Windows Deployment Services MMC snap-in, but you can set the Auto-Add policy and approve or reject pending computers. * Using the Active Directory Users and Computers snap-in. You can prestage client computers before they have attempted a network boot using AD DS. For instructions, see the section "To prestage a client computer" in How to Manage Client Computers. * Enabling the Auto-Add policy. If you enable this policy, when you approve the installation for an unknown client, the installation will proceed and a computer account will be created in AD DS for the client. For more information, see Enabling the Auto-Add Policy * Using Windows Deployment Services as part of the image installation. By default, all operating system installations using Windows Deployment Services result in a client computer that is joined to a domain. You can disable this functionality using the Client tab of the server’s properties page. Benefits Prestaging clients provides three main benefits: * An additional layer of security. You can configure Windows Deployment Services to answer only prestaged clients, therefore ensuring that clients that are not prestaged will not be able to boot from the network. * Additional flexibility. Prestaging clients increases flexibility by enabling you to control the following: o The computer account name and location within AD DS. o Which Pre-Boot Execution Environment (PXE) server should service the client. o Which network boot program (NBP) the client should receive. o Other advanced options — for example, what boot image a client will receive or what Windows Deployment Services client unattend file the client should use. * The ability for multiple PXE servers to service the same network segment. You can do this by restricting the server to answer only a particular set of clients. Note that the prestaged client must be in the same forest as the Windows Deployment Services server (trusted forests do not work). so, install WDS, reboot, verify its installed correctly and try again... cheers anyweb