anyweb

some more from this week, Task Sequence bombs out during installation of some Hotfix After looking at the SMSTS.log I found this I've googled this and I get references to Windows Update, so I've checked the windowsupdate.log file and it does list the following 2009-03-16 12:30:43:380 4868 131c COMAPI -- START -- COMAPI: Install [ClientId = wusa] 2009-03-16 12:30:43:380 4868 131c COMAPI - Allow source prompts: Yes; Forced: No; Force quiet: No 2009-03-16 12:30:43:380 4868 131c COMAPI WARNING: ISusInternal::BeginInstallUpdates3 failed, hr=80240016 2009-03-16 12:30:43:380 4868 131c COMAPI - WARNING: Exit code = 0x80240016 which didn't really help at all, long story short, to resolve this problem i had to Add a Restart within the task sequence directly after this hotfix was installed.

look at this post for some ideas

This guide assumes you are backing up an SCCM Primary Site Server, backing up a Secondary Site Server is not supported. You should always refer to Technet for best practise advise for troubleshooting, setup and maintenance of your SCCM server(s). this guide is provided as-is to help you understand the backup functionality within SCCM better and to get it working in your LAB environment, for proper guidance, refer to Technet. Create a folder for storing the data In Windows Explorer create a folder (or share on another computer *recommended) for storing our backup data eg: D:\sources\backup or \\server\someshare Create a scheduled backup task To create a scheduled backup task, expand the Site Settings node and expand the Site Maintenance node, click on Tasks. Right click on the Backup ConfigMgr Site Server task and choose properties. Set your schedule values and enable the task. What Gets Backed up ? According to Microsoft the following gets backed up: What Does Not Get Backed Up What the above doesn't tell you is that you need to backup the following (using whatever other traditional backup method you have). Using traditional backup routines (like DPM), backup the Following folders (assuming you have all your packages on D:\ if not, backup the corresponding folders on C:\ etc:- SMSSIG$ SMSPKGSIG SMSPKGD$ In other words, if you want everything backed up, you will need to backup ALL packages on ALL distribution Points you have setup, including the Package source folders using traditional backup methods (DPM etc). How can I Restore my site Backup You can restore your site backup using the Site Repair wizard, either by running splash.hta from the SCCM 2007 DVD or by selecting it from the Start Menu. How can I Restore Packages To restore packages you can use preloadpkgonsite.exe How can I manually start a backup ? Open up Administrative tools/Services and locate a service called SMS_SITE_BACKUP, select the service, right click and choose Start. At this point the SMS site backup should start, refer to the smsbkup.log file (located in D:\Program Files (x86)\Microsoft Configuration Manager\Logs) for details such as and and of course you'll want to see that it completed successfully Some Backup related reading 3 Things I learnt about SCCM backups http://myitforum.com...cm-backups.aspx Site Restore Step by Step http://myitforum.com/myitforumwp/2012/06/07/configmgr-sccm-recovery-restore-site-repair-wizard-step-by-step-guide/ Volume shadow copy service If you want to find out how ConfigMgr uses the Volume shadow copy service see here

This tip is great for incorporating Trace32.exe to your boot.wim for troubleshooting. Create folders and populate with file(s) Create a folder on your SCCM server called Extrafiles, put two blank folders in there called windows\system32 copy the trace32.exe file to the system32 folder you just created above (you can copy more than this if you wish, but for this tip this is sufficient) Create a new boot image In Operating System Deployment, right click on boot images, and choose create boot image using microsoft deployment. Point the Package Source to blank shared folder on your network. Fill in the General Settings For Image Options, use the Extrafiles folder you created above as 'extra' directories to add click next and the boot image will be created (takes some time). Note: if you get this error "Error while importing Microsoft Deployment Toolkit task sequence. Details: the ConfigMgr reported an error" then grant SYSTEM account full permissions on your network share that you are creating the boot.wim file in. Using the new boot image Dont forget to add network drivers to your boot.wim and finally dont forget to create a new Distribution Point and update it. When you are troubleshooting image deployment you can switch to this debug boot.wim by right clicking on a Task Sequence and choose properties, click on the Advanced tab and change the boot image to the one you've just created. Now when you press F8 to troubleshoot you can bring Trace32 up to read the logs right there in your deployment. btw, here's another cool way of adding trace32.exe to your boot images http://myitforum.com/cs2/blogs/1e/archive/2010/07/17/configmgr-osd-always-including-certain-files-in-your-boot-images-think-trace32.aspx

"Over the weekend, I put Windows 7 build 7000 on my desktop and Windows 7 build 7057 on my laptop, and went through trying to spot as many changes between the two as I could. Although I go deeper than I did with build 7048, this is still not a comprehensive list. There is almost three months difference between the two builds: the beta was compiled on December 12, 2008, at 2:00pm and the leaked build 7057 was compiled on March 5, 2009, at 8:00pm, so there's a lot of work to cover. This post is about tracking every noticeable visual change; although I do mention some fixes here and there, I'm mainly focusing on tweaks that are "tangible" as opposed to the thousands of bugs that have been fixed." the full story > http://arstechnica.com/microsoft/news/2009...-build-7057.ars

Windows creates a file named hiberfil.sys in the root of the system drive for systems where hibernation is enabled. The hiberfil.sys file is always the same size as physical RAM. This can be a lot of wasted space particularly if you are not using hibernation (and on a server, who is ?). so, to disable it you need to open a command prompt and type the following: powercfg.exe /hibernate off more info (vista) > http://support.microsoft.com/kb/920730 The commands to ENABLE hibernation are: powercfg.exe -h on powercfg.exe -hibernate on The commands to DISABLE hibernation are: powercfg.exe -h off powercfg.exe -hibernate off cheers anyweb

Update: RC-escrow builds are not the same as RC builds released to public and thus updated the article's title and content to reflect the same. Neowin earlier reported that Windows 7 RC is expected on April 10, 2009, but it looks like Microsoft has updated its schedule. Russian website Wzor has given some interesting tidbits about the revised 2010 TAP schedule of Microsoft. Wzor gives us the following dates related to Windows 7, Office 14 and Microsoft Exchange Server 2010. Windows 7 * The most recent build compiled is build 7061 on March 11, 2009 * Internal RC-escrow builds of Windows 7 & Windows Server 2008 R2 will be delivered to select testers on the fourth week of April 2009 * Release candidate for Windows 7 & for Windows Server 2008 R2 will be released to the public during the last week of May 2009 more info > http://www.neowin.net/news/main/09/03/16/m...s-for-windows-7

In the latest Windows 7 build (7057), recently leaked to the public, Rafael Rivera over at Within Windows has found that users can customize the UI logon background images to include custom images. Rafael reports that the functionality was probably designed for OEM manufactures to include custom images for Windows 7 in pre-configured computers, but users can now include their own images without the need to use a simple third-party program. After enabling a registry setting, users can use any image of their choice, as long as they are less than 256kb in size. First users need to enable the customization functionality by editing their regedit: HKLM\Software\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\Background Look for the DWORD value "OEMBackground" should be set the Boolean value to 1 for enabled, 0 for disabled. Depending on users systems, this value may not exist by default. Images are taken from an OEM folder located at "%windir%\system32\oobe\info\backgrounds" and may not exist by default. full story > http://www.neowin.net/news/main/09/03/16/w...-ui-backgrounds

The Remote Desktop Client in Windows 7 is equipped with new features and enhancements via Remote Desktop Protocol 7 (RDP). The most interesting enhancement is the support for Desktop Composition, full Aero glass effect. Below are the features introduced in Windows 7 Remote Desktop Client * Windows 7 Aero support * Direct 2D & Direct 3D 10.1 application support * True multi-monitor support * RDP Core Performance Improvements * Multimedia enhancements * Media Foundation support * DirectShow support * Low Latency audio playback support * Bi-directional audio support more > http://www.neowin.net/news/main/09/03/16/w...top-performance

is the vista pc joined to the domain ?

verify that your SMSadmin user is a member of Local Administrators on the target client computer, if this user is a domain admin (for testing only) then that is sufficient if your client still fails to install verify you've created a package from definition and that its correctly distributed to a DP and update the dp... cheers

you client push install account are you using ? under site settings, client installation methods, check client push installation and see if you have configured an account there, that user must be a member of Local Administrators Group on the client you are trying to install on... cheers anyweb

we need more info than that to understand your problem. when you setup sccm for the first time its quite normal until everything is configured correctly to have errors in your status logs, they should clear themselves after youve configured everything so, how have you installed everything and is wsus on the same server or on another one ?

is this an iis problem or a new problem ? if new, then start a new topic

that is normal. continue with the instructions.

if i get time in the near future i'll do it but for now i'm too busy, in the mean time read this > http://technet.microsoft.com/en-us/library/bb680838.aspx cheers anyweb

please read this post then

have you verified that IIS is indeed running by opening a web browser and going to http://localhost

what Operating system are you installing this on ?

ok read this first then checkout the Windows SIM section right here on windows-noob.com

you'll have to mount the WIM file using imageX and add them, then unmount it. cheers anyweb

Will there be a specific windows 7 SKU tailor-made for netbooks, or not? Until recently, that seemed very likely, but as time went on, the answer to that question got muddy again. During the past few weeks, Microsoft has been very adamant to reiterate that all Windows 7 SKUs can run on netbooks, and that it will enable customers to upgrade to higher SKUs easily. Recent comment by Steve Ballmer, however, indicate that Microsoft is still thinking about a specific netbook edition. more >> http://osnews.com/story/21105/Microsoft_St...s_7_Netbook_SKU

so what was the solution then in case others might have a similar problem ?

here you go http://www.windows-noob.com/downloads/BDD2007_x86.msi good luck with the exam cheers anyweb

first of all please understand that the BDD msi is out of date as it's been replaced by MDT (Microsoft Deployment Toolkit), essentially it's the same thing just with a different name however i do have a copy of BDD which i used for all the howto's here, if you still want it then let me know cheers anyweb