Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Stilez

Profile Information

  • OS
    Windows 7 x64
  • Country
  1. Like the topic says, I have just got WSUS working on Server 2012. As far as I can tell it's 100% ready now. But I notice a couple of oddities that I think I;'m doing the right thing but it's not working.... I have a default "approve all" rule, and Ive run it, but the status summary lists about 50 updates as unapproved. I can't work out why. They seem to include Silverlight and its updates, new versions of IE, and service packs (mainly for WinXP). What these seem to have in common is they are standalone items too, or may have their own licensing requirement before WU will install them - why are they "unapproved" when I have an "approve all" rule defaulted and run? I initially specified updates for Windows Vista, then unchecked those - I wont need them. But when I go to cleanup having unchecked them, I can't find any option in cleanup where it reports its removed updates as a result. It reports "0 removed". Surely if WSUS has downloaded them, then got told they arent needed or not to download them.. shouldn't it remove updates that no longer match the current "products and classifications" selection? I'm getting downloads for Itanium. I wont have any Itanium based machines - probably ever. Is there a way to exclude these?I'm hoping these are quick to fix, and help's appreciated!
  2. Quick Launch Classic 7 Tool 1.0.5

    Yeah, this should have been fixed because I spotted it on the way. Unicode was not happy, at one point I obviously mis-processed the original unicode text, and "Nouvelle barre d'outils - Choisir un dossier" was pasted into the localization strings source as "Nouvelle barre dӯutils-Choisir un dossier" and other languages the same. Meant to fix it, but obviously forgot - thanks The other translations already have English versions for you in the Localizations folder and the strings.au3 file. I've fixed the text and will upload a corrected RC 1.03 after you've had a chance to look more carefully at all of it and anything else is checked as well. If you PM me, we can check any code without flooding the forum
  3. Quick Launch Classic 7 Tool 1.0.5

    Source all included and free licensed CC-by-SA for anything I've added. Check out the "help" page, play round, check the instructions are clear (try compiling it yourself) and see what you think
  4. I figured that one out. The unattend.xml file has parallel settings to accommodate the different kinds of systems you might use it on. So if you create an unattend.xml and use it to install Win7 x32, the installer will look at the x86 items but ignore the "amd64" (MS-speak for x64) items, and if you're installing Win7 x64 the installer ignores the x86 items and looks at both amd64 and WoW64 and you probably want to set both of these. Why both amd64 and WoW64? Because 64 bit windows contains a "windows on windows" (WoW) system to handle 32 bit apps. Example: On Windows 7 x32, IE9 will be affected by settings under x86 sections. On Windows 7 x64, IE9 can be run both 64 or 32 bit, it includes both versions. IE9 64 bit (and other 64 bit s/w) will be affected by "amd64" settings and IE9 32 bit (and other 32 bit s/w) will be affected by "WoW64" settings.
  5. Quick Launch Classic 7 Tool 1.0.5

    And one last update, v2.00 RC 1.02 This update contains all the "loose ends". Changelog: Active window now usually restored afterwards. This is generally useful, in particular if the active window was something like WPI which may be showing important status information.Help now fully uses RTF and proper dialog, which makes the help easy to edit and allows it to contain and display full formatting, screenshots, and other images.Old Msgbox() calls cleaned up, old timeouts removed etc.F1 = help now (see traytip). So help is easy to get in the app, not just using command line or source files.Help files updated a lot, complete update of all text and translations.Extra user information, "how to localize", and coder information in a text file (included). The RC is about complete for me, except for bugs and improved localisation. Hope it's useful! Wazer, hope you like! Download from MediaFire / FileFactory / DepositFiles
  6. Quick Launch Classic 7 Tool 1.0.5

    Update - v2.00 RC1.01 Changelog /WAITDESKTOP - this option causes it to WAIT until both explorer.exe and the main taskbar exist before continuing. This means it will be able to work even if started by some method which causes it to execute before the desktop is created, a common issue for unattended use or slow starting sessions. Due to circumstances this will be used, it does not timeout during the time it's waiting for the desktop."LeftToRight" or "RightToLeft" language option in Locale file (handled in "help" but not yet anywhere else)/? no longer uses MsgBox, it was getting too longHelp file updates Quick Launch Classic v2.00 RC1.01.zip
  7. Quick Launch Classic 7 Tool 1.0.5

    2.00 beta RC1 With thanks to wazer and everyone, a fairly major upgrade attempt for enjoyment! Please check it carefully and improve where you can (I don't have access to multilanguage systems and can't test all its features; no reason to believe they don't work but there's surely some rough edges to discover. "Works for me" and may resolve points that others want or like Changelog Full LocalisationFull Help at command line (including backlink here)Extra options: /LOCKED and /UNLOCKED to set locked or unlocked Taskbar on exit /COPYICONS <folder> [/DISABLEOVERWRITE] to auto-copy existing icons into the QL bar at the same time. Optional switch to disable overwrite of existing icons if there's a conflict /WIDTH n to set QL bar width (in pixels, default as before is 150)Cleaner and faster window handling - several unnecessary delays removed, popup dialog now hidden, non critical mouse moves are instantOptions that should act at specific points (regardless of command line position) were executed in sequence with other parameters. Especially: If /? is specified then other options now won't be executed /EXPLORER now only executes after all registry items completeUser control of mouse/keyboard blocked at key points to prevent errors (with override instructions displayed)Explorer was always closed even when not necessary - now not needed, only closes when requestedSeveral places improved where the 1.05 code had loopholes or assumptions which could conceivably cause issues for some usersMore complete checking for success or fail on various operations with full error reporting to userBetter information (countdown, update messages via tray, etc)Windows properly restored following activity (AutoIt's WinMinimizeAllUndo() doesn't always undo all when there has been intervening activity such as popups)Unnecessary taskbar unlock/relock activity removedReplaced window titles by window handles in several functions#RequireAdmin is needed to manipulate mouse/kbd during BlockInput (AutoIt:Help:BlockInput). This is safer, but may cause a UAC prompt on some machines. The executable's properties should probably be set to "Run as Administrator" I guess (it will ask if needed, if you don't) Known issues and usage notes: Translation file needs fixing, and existing localisations need testing. Translation is direct from Google Translate with some minor fixes and therefore probably horrible Localisation in any language needs to know the Microsoft dialog title for "add new toolbar...". The localisation file is self-obvious and compiling's easy (by anyone) - please feel free to suggest other languages but the dialog title is needed first for any of them. If this can be changed (by reliably identifying the dialog by class??) then it would not be necessary to localise the core code to work with regional dialog titlesFurther testing, including testing language bar behavior, is needed. Right now "works for me" but every system is different and a lot is new or changed. General checking and improvements appreciated!TAKE CARE WHEN ADDING TO A WINDOWS INSTALL IMAGE! This code requires the desktop to already be displayed (to find the taskbar). Solutions include adding it to Startup items, or running it via a script that only launches this once the desktop's loaded. Just adding it to "Synchronous Commands" or even "First Logon Commands" and nothing else is UNLIKELY TO WORK. (see /WAITDESKTOP in RC1.01 below) Coding notes: WinMinimizeAllUndo() isn't reliable here, it can forget what windows need restore. So it's done a different way.Traytips only last 10 - 30 seconds, and vanishes upon some kinds of window manipulation. To prevent flicker the "working" tip is redrawn quite often."Don't press anything! (Esc to cancel)" self-conflicts but I figure people can work out what's meant Hopefully helpful- let me know! (And hopefully wazer will approve .... maybe ) QuickLaunchClassic_v2.00_RC1.zip
  8. Thanks Trip'. That was more intended as an example though. There's several commands that can be put in different places and I'm looking for general guidance more than help with the one specific setting. Settings where it's not sure which pass to use, or the effect of putting them in the different passes: Name, ComputerName (ie default name for new deployment) - Specialize, auditSystemReseal, ForceShutdownNow - auditSystem, auditUser, oobeSystemDriverPaths (extra mass storage + modem drivers) - offlineServicing, windowsPEInputLocale, SystemLocale, UserLocale, UILanguage - see above, I'd like to set a default locale and UI language for the installer and for the installed system, ideally with user confirmation in the installer.ShowWindowsLive - (answered already) Not as many as I thought.
  9. I'm enjoying my first toe dipping iinto sysprep, WAIK and MSIM. The actual final deployment ISO will be deployed attended but I want to make my life easy. Ideally I'd like to customise some settings and just set a more accurate default for others, so that mostly I can "default install". I don't fully understand yet what stage to add an option when there's a choice. Two examples: "ShowWindowsLive" can be added to 4 different passes: auditSystem, auditUser, oobeSystem, specializeSynchronous commands/runsynchronous can be added in quite a few different ways. Although the passes themselves are explained, Help doesn't give any obvious guide to figure out which section to put an item in, or what the effect would be of putting it in the other locations. I can't find a clear guide on google either. What I'm hoping for is clear advice or a short tutorial (or link to one) that explains how to tell which section to add an option to, if there's multiple options, or the implication of adding to different sections. Also a quick question on UI customising: of all the various unattend.xml UI options, which ones specify that by default this will be a user/system in Locale X and keyboard Y with regional settings Z, and make the finished installer default to that language/keyboard/regional setting, but allow the user to change/customise this during setup? Thanks!
  10. That's really what started this thread - the presence of two deployment systems, both recommended but no clear explanation when you might choose one rather than the other or the differences which might inform a decision. I tend to choose tweak tools that are fully featured rather than "idi ot-proof", so long as I can figure out what I'm doing. I'm happy to use MDT or not (ie manually/WAIK), and I'm fine with creating and maintaining a reference system and all that ............. so looking at the kind of things I want to do in my Win 7 image (1st post), what are the differences I'd notice between using MDT vs. manual/WAIK methods to create the .iso? Update - Apparently "id***-proof" is caught by the forum filter!
  11. That's about the level of detail I needed to fill in the gaps after reading up on it. Thank you. My main remaining questions are: Sounds like I don't need to worry about MDT. Does it have any real use for me? I found this: "On reboot, you'll automatically be logged in under the built-in Administrator account. A sysprep GUI box will appear, but you can close it and NOW begin to customize your profile. Install any software/drivers, make any profile customizations, etc. If you need to reboot, the computer will boot you back into the Administrator account. You will be stuck in this audit mode until you run sysprep with the /oobe parameter. After doing so, sysprep will delete/clean up the Administrator account, but if you have copyprofile=true in your unattended answer file, it will copy the customized Admin account to the default profile before deleting it." I hadn't realised that the admin account would be generalised and set up as the default profile. That helps a lot. I've probably got enough of the gaps filled now to check my other questions for myself when I try i Thanks!
  12. I'm creating a custom installer for Windows 7 x64. The tools look fairly straightforward so far (WAIK, MDT, DISM, SIM) but there seem to be quite a few tools and choices of approach. I'm a regular VMware user so I'm confident about installing a reference version of Windows onto either VMware or a spare hard drive, and I'm fine with cloning a VMware install to create a version for sealing. The machines I'm installing will mainly be "one user account + admin" systems (family, friends, test systems, etc). Any customisations or settings should be applied to all users. The official Microsoft tools seem to allow more customisation than packagers like rt7lite so I'm fine with those. What I want in my custom install is - Win 7 SP1 and other updatesInstaller customisations using System Image Manager or similarOther settings changes - registry tweaks, a few ACL permission changes, group policy settings, IE9 settings and security zones, etcA bunch of default user interface settings - default theme, desktop, display, icon sizes, taskbar, etcVarious software, utilities and applications (ms office, classic shell, treesize, firefox, etc) and their settings once installedThe final installer needs to run WPI automatically. I use WPI to handle a few customizations which vary, and also for silent install of the latest drivers for various platforms. My questions: I don't fully understand the difference between WAIK, MDT, DISM, and SIM having never used any of them (though they all seem straightforward). A short recap of their different roles and the differences between them would help, so I'm not confused.Which of these tools would be recommended to use? What should my process look like in summary?If the reference system is on VMware 7.x, I'm guessing I copy the VM, boot the copy to the chosen snapshot, and then generalize it, creating an installer based on that snapshot? Is that correct?Does generalizing removes the current choice of driver so that when Windows installs, it chooses "the most suitable drivers" like the usual DVD would?How do I ensure that customisations like user interface stuff, installed software, regedits, group policies, etc aren't lost during the generalizing process?Is this the way to make customisations on the reference system be applied as the default for new accounts, so that all users created on the new system will inherit them?How do I get WPI to run after installing?As I understand it, the process creates a Windows installer ISO which I use to create a bootable USB drive. What's the right tool for that step? (I would need both ISO and bootable USB versions)Anything else I need to be aware of? I should be able to work most of the rest out from the excellent tutorials online, but I would like to make sure I'm using these powerful tools the right way. Thanks
  13. Win7 SP1 says it both succeeded and failed...?

    Web install fixed it. What a poorly designed popup though!
  14. Win7 SP1 says it both succeeded and failed...?

    What you see there is after I clicked "show details". It showed the error message DS_S_SUCCESS and a zero error code. It doesn't show SP1. What on earth does it mean that it both succeeded and didn't succeed, with an "error code" being DS_S_SUCCESS?
  15. Apparently installing Win 7 SP1 was both "not successful" and "completed successfully". Relatively recent x64 clean install (1 month ago) using SP1 offline 900 MB package, appeared to work, but popped up this interesting message when completed. Windows Update still shows SP1 as available to install. Any ideas what it means?