WinSxs folder in Windows 7 deployment

Hi
I know the topic of the size of the Winsxs has been done to death a bit but I wonder if anyone can help me.
I've installed a fresh copy of Windows 7 64 bit SP1 from an ISO.
Without installing any updates or any applications the Winsxs folder is 5.5GB.
I've run disk cleanup and it doesn't make any significant difference.
Running
DISM /online /cleanup-image /spsuperseded /hidesp
gives the message
Service Pack Cleanup can't proceed: No service pack backup files were found.
does anyone know a way to install Windows 7 without starting out with such a large WinSXS folder?

Hi,
I consider 5.5 GB is not too big size for this folder. The component store (WinSxS folder) contains all the components that make-up Windows to allow you operate your system. These components are kept to rollback any problematic change or to repair a file
that becomes corrupted.
For operating system files, it can appear that more than one copy of the same version of a file is stored in more than one place on the operating system, but there’s usually only one real copy of the file. The rest of the copies are just “projected” by hard
linking from the component store. A hard link is a file system object that lets two files refer to the same location on disk. Some tools, such as the File Explorer, determine the size of directories without taking into account that the contained files
might be hard linked. This might lead you to think that the WinSxS folder takes up more disk space than it really does.
This blog could be referred:
Breaking News! Reduce the size of the WinSxS Directory and Free up Disk Space with a New Update for Windows 7 SP1 Clients
http://blogs.technet.com/b/askpfeplat/archive/2013/10/07/breaking-news-reduce-the-size-of-the-winsxs-directory-and-free-up-disk-space-with-a-new-update-for-windows-7-sp1-clients.aspx
Karen Hu
TechNet Community Support

Similar Messages

How to reduce size of C:\Windows\winsxs folder in windows 2008 R2?

Hello,
Is there any way to reduce size of C:\Windows\winsxs folder in windows 2008 R2
simular to
DISM /online /Cleanup-Image /SpSuperseded
Many thanks

Okay maybe some background on the root of the problem would help.
Windows XP (and Windows 2000) used a fast and great mechanism called Hotfix Installer (Update.exe) to install updates. Updates installed in very little time. If you wanted to further reduce update times on Windows XP, you could just temporarily stop the
System Restore service and updates would install at crazy speeds. Note that this is not recommended for novice users who don't know advanced recovery methods, as some updates can sometimes cause your system to stop booting so you cannot even uninstall them.
The method the Hotfix Installer used was simple, it just installed a new version of files to be updated at %windir%\system32 and %windir%\system32\dllcache (the Windows File Protection cache). For files that were in use, a restart copied them from dllcache
to the system32 folder. This is simple file-based servicing. The hotfix installer (Update.exe) also supported various command line switches like /nobackup which means not to backup files it patches. Again, this is not recommended for novice users as some updates
can screw your system even after the comprehensive testing Microsoft does before releasing them. But if you won't be uninstalling any updates (usually one only requires uninstalling updates if they cause problems), you could save a ton of disk space by not
backing up the files it patched. The Hotfix Installer backed up files to C:\Windows\$Uninstall$KBxxxxxx folders so even if you did back up the files at install time, they could be safely deleted after a few days if no stability issues were found after using
Windows with the newest updates applied. Update.exe also supported the very important and convenient ability to slipstream a service pack or update into the original Windows setup files using the /s switch.
When Microsoft was developing Windows Vista, they realized that components had gotten too many interdepencies on each other and to service each file reliably without breaking another component that relied on it, Microsoft introduced what they called as Component
Based Servicing (CBS). You can read all about it in a much more technical way at The Servicing Guy's blog. What CBS does basically is it installs all files of the entire operating system, including all languages into C:\Windows\WinSxS and then it hard-links
files from there to C:\Windows\system32. This has the benefit of not having to insert the OS disc to add or remove any components, and some other advantages as well like offline servicing of a Windows Vista or Windows 7 image. But the design introduces a major
disadvantage of taking up a lot of hard disk space. Whenever an update is installed, it no longer installs it to C:\Windows\system32 and C:\Windows\system32\dllcache like Windows XP's hotfix installer (Update.exe) did. Instead, it updates the files in C:\Windows\WinSxS.
Now, Windows keeps multiple copies of the same file but with different version in WinSxS if it is used by more than one Windows component. The higher the number of components, that many number of times the file exists in C:\Windows\WinSxS. When a Windows Vista
update (.MSU) is installed, the components get updated, each and every one, instead of the files and the worst part is it still maintains the older superseded previous versions of components in WinSxS so the user would be able to uninstall updates. Microsoft
does say that some sort of "scavenging" or deleting older copies of components takes place but is scarce on the details. The scavenging seems to take place automatically at certain intervals in Windows 7 but not in Windows Vista. In Windows Vista, you have
to add or remove any Windows component for the scavenging to take place. And Microsoft says the scavenging will free up some disk space but in practice, on my system, I see my free disk space only decreasing on Vista as I remove or add any component. Windows
does not give the user an option to not backup the earlier versions of components like Windows XP's /nobackup switch in Hotfix Installer did. As as you install more and more updates on your system, they will take more and more disk space. This is one of the
primary reasons Windows Vista and Windows 7 are so bloated. Another reason for them being so bloated is the DriverStore that these OSes store. All drivers that are shipped with the OS and the OEM ones which you download and which are installed for a particular
system are staged in C:\Windows\System32\DriverStore. But let's not go there for now.
Now, an important thing to note is that the size of the WinSxS folder is not what Explorer or the dir command report, it is far less but is misreported by Explorer because it counts the hard links more than once when calculating size. That does not mean,
the size of WinSxS is not causing real-world disk space problems on numerous Windows Vista/7 systems in use today. Microsoft's ingenious recommendation to this problem of ever growing disk consumption is to install fewer updates to keep the size of the servicing
store under control. Of course, users cannot deny installing security updates and leave their system open to security holes. What they can do is install less optional updates, the ones that Microsoft releases on the fourth Tuesday of every month and also install
less of the hotfixes that are available by request from a Knowledge Base article. In short, you have to trade the number of bugs fixed in the OS by installing hotfixes at the cost of enormous amounts of disk space. The whole servicing stack is a total downgrade
to Windows XP's update.exe method. It causes heavy disk thrashing and slow logoffs/logons while Windows configures these updates at the Welcome Screen. Many systems are unable to boot because of failed updates. Another disadvantage of the "new" servicing stack
(and the redesigned Setup mechanism of Windows Vista) is the inability to do a true slipstream of service packs and hotfixes.
The time it takes to actually install these hotfixes online compared to Windows XP is also completely unacceptable. When you start installing an MSU update, it spends a lot of time determining whether the update applies to your system. Then, the update itself
takes much longer to install compared to Windows XP's Update.exe (hours instead of minutes if you are installing dozens of updates through a script). Finally, that post-installation process ("Configuring updates... Do not turn off your computer") takes several
minutes before shut down followed by a second post-installation process (configuration) upon restart before logon that also takes also several minutes and thrashes the disk.
I can install the entire SP3 for Windows XP in about 10 minutes after downloading the full installer. I can also install a slipstreamed-with-SP3 copy of Windows XP is about 45 minutes on a modern fast PC. In contrast, Windows Vista or Windows 7 do install
relatively quickly (in just about 15-20 minutes) on a modern PC but installing the service packs and updates takes more time than anything on XP did. Not only can service packs not be slipstreamed, but Vista Service Packs are not even cumulative, which means
if you clean install Windows Vista today, you have to install SP1 first which takes about 90 minutes, then SP2 which takes less time, then all the post-SP2 updates which do take hours to install. If you really HAVE to use Windows 7 or Windows Vista, you are
stuck with this slow update non-sense as Microsoft does not even acknowledge that there is any slowdown or loss of functionality in the new servicing mechanism. The fact remains: MSU updates are slow as **** and take too much time and as Windows 7/Vista get
older and Microsoft stops producing service packs, a clean install is going to take longer and longer to bring it up-to-date with all patches installed. Is is worth wasting your time on an OS whose servicing mechanism Microsoft completely screwed up? I once
again recommend you read more about the servicing stack and how it operates at The Servicing Guy's blog:http://blogs.technet.com/b/joscon/. To fix this messed up servicing stack, Microsoft also offers a tool
called CheckSUR for your system if it finds “inconsistencies in the servicing store”.
Microsoft's Windows Vista and Windows 7 products are not engineered with disk space in mind. It causes a problem, especially for SSDs which are still low capacity and very expensive. The only hope is that Microsoft again completely redesigns this servicing
mechanism in a future Windows release so it would not cause this growing disk space consumption issue, speed up installation of updates by an order of magnitude, not slow down logon and logoff, not prevent systems becoming unusable because of failed updates
being stuck at a particular stage and allow true slipstreaming.
Microsoft's response to this is vague - they simply state "Windows 7's servicing is more reliable than Windows XP" but they cannot acknowledge it is a million times slower and still unreliable...slow to the point of being unusable and sometimes leaving systems
in an unbootable damaged state. Of course they know all this too but can't admit it since it makes their latest OSes look poor. Moving from a very simple and fast update mechanism that worked to a complex one that requires endless “configuring” and repair
through CheckSUR is a product engineering defect.
Take a look at servicing-related complaints in Microsoft's own forums:
1.
Very slow install of updates to Windows 7
2.
Windows 7 - Updates are very slow
3.
Windows 7 Ultimate, it takes long time configuring updates
4.
"Preparing To Configure Windows. Please Do Not Turn Off Your Computer"
5.
Very slow update install at shutdown (Windows 7 Home Premium)
6.
Why does my computer run so slow when installing updates?
7.
Every time the computer is shut down, it always says installing update do not turn off your computer
8.
Computer is working slow and wants to do windows updates all the time
9.
Windows 7 Update install time taking a very long time
10.
Windows wants to install 6 updates every time I log off or put the computer in sleep mode
11.
Problem In Configuring Windows Updates at the time of Startup
12.
Computer really slow after latest updates
13.
Windows hangs up in "configuring updates"
14.
Why can't windows 7 install updates?
15.
Every time computer is shut down, receive Installing updates, do not shut off....
16.
How long does it take for the Windows 7 Home Premium updates take?
17.
Windows 7 "Installing Update 2 of 2" for 12 hours now
18.
Updates causes endless reboots
19.
Updates stuck installing for over 24 hrs. Computer does not boot
20.
Cannot load Windows 7 after installing 2 critical updates
A proper solution to this problem would be to completely re-engineer and rewrite the servicing mechanism so it operates with the speed, reliability and pain-free operation of the XP servicing mechanism.
I don't see this situation improving in Windows 8 either. Good luck with your Windows tablet taking hours to install service packs and updates. Now, do iPads take that long to install updates?
Microsoft understated the real system requirements to keep a Windows 7/Vista system running. System requirements at install time may be 15 GB of free disk space but over time, this number increases to alarming levels as you install more service packs and
post SP-updates. You can find out the real size of the WinSxS folder using a tool like cttruesize (ctts.exe) (download it from
http://www.heise.de/software/download/cttruesize/50272 and run ctts -la -a -l C:\Windows to find the correct size minus the hard links which MS says causes Explorer to misreport the WinSxS
folder size but the fact remains that even with the correctly calculated size of WinSxS, the disk space requirements of Windows 7 to keep it updated are unacceptable, especially for people's SSDs which are running out of disk space!

Cleanup WinSxS folder of Windows 7 Sp1

Microsoft released an update to cleanup WinSxS.
Go this this KB article and install the update:
Update is available that enables you to delete outdated Windows updates by using a new option in the Disk Cleanup wizard in Windows 7 SP1
http://support.microsoft.com/kb/2852386
When you now launch the disk cleanup (as admin) you get an option "Windows Update Cleanup":
Click ok to start cleanup. now you must reboot Windows 7. After the reboot you get a screen which shows you that cleanup happens:
You can get more information here:
Breaking News! Reduce the size of the WinSxS Directory and Free up Disk Space with a New Update for Windows 7 SP1 Clients
http://blogs.technet.com/b/askpfeplat/archive/2013/10/08/breaking-news-reduce-the-size-of-the-winsxs-directory-and-free-up-disk-space-with-a-new-update-for-windows-7-sp1-clients.aspx
"A programmer is just a tool which converts caffeine into code"

Horinius - you have to reboot for the clean up to occur. WHen I did, it cleaned up the amount of disk space that the Cleanup manager said, but my winsxs folder had about 8 GB more, most of which is files and folder that at 3+ years old. My theory is that
this is garbage that my IT department left behind when they build the standard image.
Anyone know how to delete the rest of the trash in WinSxS?
Of course we have to reboot for the clean up. Did I say we didn't have to?
If you want to do the "Windows Update cleanup" (as specified in the original post), there's no need to use this "Cleanup manager". You just need to open "C:\Windows\SoftwareDistribution\Download" and delete everything inside it.
Please read carefully my posts before commenting.

Can I still uninstall any windows updates after clean up the winsxs folder by dism on Win2008 R2 SP1?

Hi,
Just a general question about Dism, does the cmd below only focus on serivce pack clearn up or I wont able to uninstall any windows updates at all after the clean up?
dism.exe /online /cleanup-image /spsuperseded
Regards
Anders

Hi,
The service pack cannot be uninstalled after this command is completed.
Clean Up the WinSxS Folder
http://technet.microsoft.com/en-us/library/dn251565.aspx
How to reclaim space after applying Windows 7/2008 R2 Service Pack 1
http://blogs.technet.com/b/joscon/archive/2011/02/15/how-to-reclaim-space-after-applying-service-pack-1.aspx
Hope this helps.

MDT 2012U1 / Windows 8 deployment - impossible to add a role when deploying windows with language pack

Hello,
I am having a problem deploying Windows 8 with language packs and adding at the same time a role/feature (netfx3).
What I have done is creating a Standard Client Task Sequence. In the task sequence I have added, in the State Restore phase, the step Install Roles and Features (where only .Net Framework 3.5 is selected). I have configured nothing else !
If I use this task sequence, everything is ok; Windows 8 is well deployed and NetFx3 feature is installed.
Now, if I add one or more language packs in the MDT console and select them when using the previously created task sequence, the deployment fails with one error : ERROR - NetFx3 role processing with DISM.exe failed, rc = -2146498529.
The language packs are well installed but as the error message says, NetFx3 is not installed.
In the ZTIOSRole.log I can find this :
<![LOG[Microsoft Deployment Toolkit version: 6.1.2373.0]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[The task sequencer log is located at C:\Users\ADMINI~1\AppData\Local\Temp\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log.]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1"
thread="" file="ZTIOSRole">
<![LOG[Roles will be installed.]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OSRoles.]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OSRoleServices.]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Features specified in Feature:]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ NetFx3]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OptionalOSRoles.]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OptionalOSRoleServices.]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OptionalOSFeatures.]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ZTI Heartbeat: Processing roles (0% complete]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Event 41003 sent: ZTI Heartbeat: Processing roles (0% complete]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Validating connection to \\HPZ820\ZENPROD01$\Operating Systems\W8ENTSP0x64]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread=""
file="ZTIOSRole">
<![LOG[Already connected to server HPZ820 as that is where this script is running from.]LOG]!><time="12:55:05.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Copying source files locally from \\HPZ820\ZENPROD01$\Operating Systems\W8ENTSP0x64\sources\sxs]LOG]!><time="12:55:05.000+000" date="10-24-2012" component="ZTIOSRole" context=""
type="1" thread="" file="ZTIOSRole">
<![LOG[About to execute command: cmd.exe /c C:\windows\system32\DISM.exe /Online /Enable-Feature /FeatureName:"NetFx3" /Source:"C:\MININT\sources\X64" /LimitAccess /All /NoRestart /logpath:C:\MININT\SMSOSD\OSDLOGS\ZTIOSRole_Dism.log >> C:\MININT\SMSOSD\OSDLOGS\ZTIOSRole_DismConsole.log]LOG]!><time="12:55:24.000+000"
date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ERROR - NetFx3 role processing with DISM.exe failed, rc = -2146498529]LOG]!><time="12:55:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="3" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles001 is now = NETFX3]LOG]!><time="12:55:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Role processing complete.]LOG]!><time="12:55:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ZTIOSRole processing completed successfully.]LOG]!><time="12:55:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Event 41001 sent: ZTIOSRole processing completed successfully.]LOG]!><time="12:55:58.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
If I take the same log file from a machine where I have used the same task sequence but without deploying language packs, I can find that :
<![LOG[Microsoft Deployment Toolkit version: 6.1.2373.0]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[The task sequencer log is located at C:\Users\ADMINI~1\AppData\Local\Temp\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log.]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1"
thread="" file="ZTIOSRole">
<![LOG[Roles will be installed.]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OSRoles.]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OSRoleServices.]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Features specified in Feature:]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ NetFx3]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OptionalOSRoles.]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OptionalOSRoleServices.]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OptionalOSFeatures.]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ZTI Heartbeat: Processing roles (0% complete]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Event 41003 sent: ZTI Heartbeat: Processing roles (0% complete]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Validating connection to \\HPZ820\ZENPROD01$\Operating Systems\W8ENTSP0x64]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread=""
file="ZTIOSRole">
<![LOG[Already connected to server HPZ820 as that is where this script is running from.]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Copying source files locally from \\HPZ820\ZENPROD01$\Operating Systems\W8ENTSP0x64\sources\sxs]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context=""
type="1" thread="" file="ZTIOSRole">
<![LOG[About to execute command: cmd.exe /c C:\windows\system32\DISM.exe /Online /Enable-Feature /FeatureName:"NetFx3" /Source:"C:\MININT\sources\X64" /LimitAccess /All /NoRestart /logpath:C:\MININT\SMSOSD\OSDLOGS\ZTIOSRole_Dism.log >> C:\MININT\SMSOSD\OSDLOGS\ZTIOSRole_DismConsole.log]LOG]!><time="14:00:20.000+000"
date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[NetFx3 role processing succeeded, rc = 0]LOG]!><time="14:03:50.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles001 is now = NETFX3]LOG]!><time="14:03:50.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Role processing complete.]LOG]!><time="14:03:50.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ZTIOSRole processing completed successfully.]LOG]!><time="14:03:50.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Event 41001 sent: ZTIOSRole processing completed successfully.]LOG]!><time="14:03:51.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
As you can see, in both logfile, the source are copied from the same folder.
Does anyone have an idea ? what am I missing ?
I have easily reproduced the problem on another computer (installing ADK/MDT, installing OS and creating task sequence).
Thanks in advance for your help.
Marc.

Hello,
Workaround:
1. copy stock sxs folder to local disk (e.g c:\sxs)
2. make a direct internet connection (don't use proxy!)
3. open admin command prompt and type: DISM.exe /online /enable-feature /featurename:NetFX3 /All /Source:c:\sxs
4. after the successful install find the c:\windows\winsxs folder and sort by date
5. copy new folders (that are equal to current date) to deployment share's sxs folder (overwrite)
And now, try standard MDT install (create "Install Role And Feature" step in the Task Sequence, enable .NET install).

WinSXS folder during capture

I was just watching my capture process this morning and I got to thinking:
The WinSXS folder contains all the roll-back data for Windows updates etc. With no SP2 on the horizon for Windows 7 a LOT of updates get installed during the capture process.
Does anyone have any information on whether this WinSXS folder gets cleared/cleaned during the Sysprep/Capture process? I cant seem to find any direct information on it.
These update will never need to be rolled back. Always after a quicker, slimmer image - I would hate to think that my deployment image contained 100's of MB's (or even GB's) of completely unnecessary data.

Hi,
I genuinely advise you not to mess with the WinSXS folder yourself.
Very recently a Windows update has been released that adds an option to the disk cleanup wizard which deletes Windows Updates from the update cache.
Check these links:
http://support.microsoft.com/kb/2852386
http://windowsitpro.com/windows-7/microsoft-releases-windows-updates-cleanup-utility-add-windows-7-sp1
http://www.tweakhound.com/2013/10/09/windows-update-cleanup-for-windows-7-and-windows-8/
http://lifehacker.com/recover-tons-of-wasted-disk-space-with-the-new-windows-1442937625
Make sure this update is present in your image, then you can embed an
CLEANMGR SAGESET which allows you to cleanup these updates automatically, run this step before the sysprep and capture, and all updates and contents that can be deleted will be deleted.
Good luck!
If this post is helpful please click "Mark for answer", thanks! Kind regards

Best practice for managing a Windows 7 deployment with both 32-bit and 64-bit?

What is the best practice for creating and organizing deployment shares in MDT for a Windows 7 deployment that has mostly 32-bit computers, but a few 64-bit computers as well? Is it better to create a single deployment share for Windows 7 and include both
versions, or is it better to create two separate deployment shares? And what about 32-bit and 64-bit versions of applications?
I'm currently leaning towards creating two separate deployment shares, just so that I don't have to keep typing (x86) and (x64) for every application I import, as well as making it easier when choosing applications in the Lite Touch installation. But I know
each deployment share has the option to create both an x86 and x64 boot image, so that's why I am confused.

Supporting two task sequences is way easier than supporting two shares. Two shares means two boot media, or maintaining a method of directing the user to one or the other. Everything needs to be imported or configured twice. Not to mention doubling storage
space. MDT is designed to have multiple task sequences, why wouldn't you use them?
Supporting multiple task sequences can be a pain, but not bad once you get a system. Supporting app installs intelligently is a large part of that. We have one folder per app install, with a wrapper vbscript that handles OS detection. If there are separate
binaries, they are placed in x86 and x64 subfolders. Everything runs from one folder via the same command, "cscript install.vbs". So, import once, assign once, and forget it. Its the same install package we use for Altiris, and we'll be using a Powershell
version of it when we fully migrate to SCCM.
Others handle x86 and x64 apps separately, and use the MDT app details to select what platform the app is meant for. I've done that, but we have a template for the vbscript wrapper and its a standard process, I believe its easier. YMMV.
Once you get your apps into MDT, create bundles. Core build bundle, core deploy bundle, Laptop deploy bundle, etcetera. Now you don't have to assign twenty apps to both task sequences, just one bundle. When you replace one app in the bundle, all TS'es are
updated automatically. Its kind of the same mentality as active directory. Users, groups and resources = apps, bundles and task sequences.
If you have separate build and deploy shares in your lab, great. If not, separate your apps into build and deploy folders in your lab MDT share. Use a selection profile to upload only your deploy side to production. In fact I separate everything (except
drivers) into Build and deploy folders on my lab server. Don't mix build and deploy, and don't mix Lab/QA and production. I also keep a "Retired" folder. When I replace an app, TS, OS, etcetera, I move it to the retired folder and append "RETIRED - " to the
front of it so I can instantly spot it if it happens to show up somewhere it shouldn't.
To me, the biggest "weakness" of MDT is its flexibility. There's literally a dozen different ways to do everything, and there's no fences to keep you on the path. If you don't create some sort of organization for yourself, its very easy to get lost as things
get complicated. Tossing everything into one giant bucket will have you pulling your hair out.

How to cleanup the winsxs folder in 2008 r2

I have searched throughout this site and still not found an answer to how to miminse the size of the winsxs folder.
regardless of if the files are actually there or hardlinks or etc, the fact is that somefiles somehwere on the drive are using all the free space and windows reports that it is taking up 18GB on a 30Gb drive. and we are constantly running out of
free space and exchange stops working. This server is not used for anything but exchange and the logs and data are on other drives.
Now please direct me to a fix for this issue as the OS should not be consuming this much free space.

Hi,
Thank you for the post.
Please read KB2592038:
To remove the Service Pack files from a Windows installation use the following in-box utilities:
Windows 7 or Windows Server 2008 R2 Service Pack 1: DISM /online /Cleanup-Image /SpSuperseded or Disk Cleanup Wizard (cleanmgr.exe)
If there are more inquiries on this issue, please feel free to let us know.
Regards
Rick Tan
TechNet Community Support

Windows Azure deployment with Eclipse plugin

Hi everybody!
I want to deploy a windows azure deployment project.
Here is my problem:
When i create the project there is no samples folder, so i can't edit my startup.cmd to make it run. I don't know how to edit the startup.cmd by my own. I am using tomcat 7.0.34. I would need a sample how to write the startup.cmd to make my project run.
It would be great if you could show me an example of a startup.cmd for tomcat and explain what's going on there.
Another thing i want to ask is if i have to join the zipped jdk folder to the approot folder or the jre folder. I have seen both ways in different tutorials and this confuses me.
I hope you can help me!

Hi,
Seems you have some issue in deploy windows azure project to Windows Azure, I didn't very familiar with java, hope the following links give some help.
#http://msdn.microsoft.com/en-us/windowsazure/ee941631.aspx
#http://java.interoperabilitybridges.com/articles/deploying-a-java-application-to-windows-azure-with-command-line-ant
#http://java.interopbridges.com/articles/deploying-a-java-application-to-windows-azure-with-eclipse
Best Regards
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Windows 8 deployment using Zenworks imaging services

Hi,
I would like to find some guidelines or best practices stuff in order to help me with the deployment of Windows 8.1
For our current method with Windows 7, we used SYSPREP with offline drivers for multiples machines in a local folder ex. C:\Drivers.
Now it seems that it won't work anymore with Windows 8, and when we ask for help in the Microsoft forums we are pushed to products like MDT,WDS and SCCM.
Does anyone here had a successful Windows 8 deployment ?
Thank you in advance for your input

Originally Posted by anto28
Yes i have
I asked this question a multiple forums but i have not received any satisfying answer yet...
Can you elaborate with the DPinst way ?
At what point do you use this command to inject drivers ? In the audit mode ?
I think DPInst require the hardware to be present in order to work, no ?
What if you want to install drivers for 7-10 different machine type in your image ?
Thank you Thomas.
Simply put, you call dpinst on first login after the image is deployed on the workstation by adding the following to sysprep unattend xml:
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<CommandLine>c:\drivers\dpinst.exe /path C:\drivers\pnp</CommandLine>
<Order>1</Order>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>
and dpinst xml should look something like this:
<?xml version="1.0" ?>
<dpinst>
<search>
<subDirectory>*</subDirectory>
</search>
<legacyMode/>
<quietInstall/>
<suppressWizard/>
<scanHardware/>
</dpinst>
You could add all the drivers to the base image or then use addon images for specific workstations models that places the workstation specific driver into: C:\drivers\pnp.
Thomas

Can't rename a folder in Windows 7 - receive error message

When trying to rename a folder in Windows 7, I get a "Folder In Use" message saying that the folder or a file in it is open in another program. This is untrue as I don't have any other programs open. I even rebooted the computer and tried again
and it gave me the same message. This has occurred more than once and it's beginning to drive me crazy. Do you have any suggestions as to how to fix this problem?

Hi,
Please use the
Process Explorer to check which process keeps your file in use.
In addition, you can try to rename the folder in
Safe Mode to see the result.
For more reference,
Troubleshooting with Process Monitor
Hope this helps
Vincent Wang
TechNet Community Support

Creating a New Folder in Windows Registry by java coding

Good morning,
hi to all,
how can I create a New folder in Window Registry using Java coding. Can anybody help me out pls.
I begin waiting for ur reply.
Thanx

Why do you feel you need to write to the Windows registry directly? Take a look at the Preferences class.
{color:#0000ff}http://java.sun.com/javase/6/docs/api/java/util/prefs/Preferences.html{color}
luck, db

Create a new folder in windows from SAP

Hi,
I can execute progrmas from sapusing the WS_EXECUTE function, but how can I crete a new folder in windows from SAP?.
Thnaks

Hi,
I have a idea about this problem.
Firstly, I made a batch file. The file is a text file, so you can create easily the file from the WS_DOWNLOAD function. The file include a command - md (folder name).
Secondarily, I executed the batch file by the function 'WS_EXECUTE'.
Finally, I deleted the temporary file by the WS_FILE_DELETE function.
It's easy.
If do you need the source, you should send a mail to me.
The source is given you.
Best regards,
Don

How to get the print logs to appear in the application logs folder of windows server 2008 r2

Dear All,
I am a SIEM professional at an IT firm. i am facing a problem. My SIEM solution has an agent for windows. this agent reads only logs from the application, security and system folder of windows event viewer. In server 2008 r2 the printer logs are clustered
in and application and services/microsoft/windows/print services folder. The requirement of my management is that the siem solution should also be able to montior compliance of print policies. that can only be done once the the print logs are viewable in any
of the three event vieweer folders i.e application, system.security. how can i configure windows to make its print logs visible in any of these three folders ?

this may be helpful...
http://social.technet.microsoft.com/Forums/windowsserver/en-US/fe8892cc-fb6d-49c7-8b2d-c1f17df8e085/2008-r2-use-advanced-security-audit-policy-to-log-print-jobs?forum=winserverprint
or post here...
http://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserverprint
Best,
Howtoto

Can't see icloud drive folder in Windows 7

Hi all,
I'm running Windows 7 and icloud 4.0.
I'm familiar with apple products, and have followed all requirements to enable icloud drive on my ipad and iphone.
However I am unable to find the icloud drive icon/folder in Windows explorer on my PC.
When I select the checkbox to enable icloud drive within icloud on my PC then press 'apply', nothing happens. If I close icloud and then re-open it, the checkbox has returned to the unchecked state.
I've tried uninstalling then reinstalling icloud, no difference.
By the way, it all seems to run fine on my Windows 8 devices.
I can't find anyone else with a similar issue...any suggestions?
Thanks in advance.

Great you have figured it out finally. Just thought you should know that there is a bug in 11gR2 client and because of that Oracle driver version is shown as 11.1.0.7 instead of 11.2.0.2. This can be confusing 6 months or a year later down the road if you wanted to go back and upgrade your client to, let's say' 12g. To fix this, there is a patch available from Oracle metalink, patch id is p11731183 for 32bit and p11731184 for 64bit windows. This bug is mentioned in 1308617.1

WinSxs folder in Windows 7 deployment

Similar Messages

Maybe you are looking for