Jump to content


anyweb

Root Admin
  • Posts

    9210
  • Joined

  • Last visited

  • Days Won

    367

Everything posted by anyweb

  1. try doing it in Windows PE instead, it's designed for Windows PE not Windows. cheers niall
  2. We have said that Windows 8 is a complete reimagination of the Windows operating system. Nothing has been left unexplored, including the Windows logo, to evaluate how it held up to modern PC sensibilities. The Windows logo is a strong and widely recognized mark but when we stepped back and analyzed it, we realized an evolution of our logo would better reflect our Metro style design principles and we also felt there was an opportunity to reconnect with some of the powerful characteristics of previous incarnations. We had a very short list of agencies that we wanted to work with on the redesign of the logo and were thrilled when Pentagram agreed to join us in the project. Pentagram’s illustrious history speaks for itself, but we were particularly attracted to their sense of classic graphic design which fit well with our Metro design principles. Early in the development cycle for Windows 8, in a conference room on the Microsoft campus, we assembled a kick off meeting with Paula Scher, Michael Beirut and Daniel Weil from Pentagram and a few designers and marketing leaders from Windows and across the company. The team spent a full day sharing some of the Metro style design philosophy; the Windows brand history and values as well as graphic design and technology industry trends. "To see what is in front of one's nose needs a constant struggle."- George Orwell That is the feeling we had when Paula Scher (from the renowned Pentagram design agency) showed us her sketches for the new Windows logo. It’s a window… not a flag Paula asked us a simple question, “your name is Windows. Why are you a flag?” In some ways you can trace the evolution of the Windows logo in parallel with the advancements of the technology used to create logos. From the simple two color version in Windows 1.0 to the intricate and detailed renderings in Windows Vista and Windows 7, each change makes sense in the context in which it was created. As computing capabilities increased, so did the use of that horse power to render more colors, better fonts, and more detailed and life-like 3D visual effects like depth, shadows, and materiality. We have evolved from a world of rudimentary low resolution graphics to today’s rich high-resolution systems. And what started as a simple “window” to compliment the product name became a flying or waving flag. But if you look back to the origins of the logo you see that it really was meant to be a window. "Windows" really is a beautiful metaphor for computing and with the new logo we wanted to celebrate the idea of a window, in perspective. Microsoft and Windows are all about putting technology in people's hands to empower them to find their own perspectives. And that is what the new logo was meant to be. We did less of a re-design and more to return it to its original meaning and bringing Windows back to its roots – reimagining the Windows logo as just that – a window. Let’s look back at a few of the versions along the way. Windows 1.0 Few remember the original Windows logo, yet we found it both refreshing and inspiring in relation to the work we have been doing on the Metro style design visuals. Using simple lines and clear straight forward concept, this logo reminded us of what a great and evocative name we have with “windows”. Windows 3.1 For many of us this was the image in our mind when we think of past Windows logos. The now classic window shape and the introduction of the four colors were hallmarks of the Windows brand for many years to come. The introduction of the “waving effect” gives the logo a sense of motion. This logo would be the basis of the Windows versions throughout the 1990s. Windows XP The next major incarnation of the logo came with the release of Windows XP. What has come to be known as the “Windows flag” is a cleaner more sophisticated mark than its predecessors. The version that populated the lower left hand corner of Windows PCs next to the word “Start” also gained a sense of materiality (plastic?) and a 3D effect from the rich gradients and shadows. Windows Vista The Windows Vista release marked the beginning of the AERO design aesthetic in Windows with a key component of the interface being the “AERO glass” effect. Replacing the green Start button was the round glass-like button with a now flattened version of the “flag” from Windows XP. Internally, this icon became known as the “pearl”. You can see the intricate lighting effects of the faux glass. In many ways signaling just how powerful of a rendering engine the PC had become. This version of the logo was largely unchanged for Windows 7. Windows 8 With Windows 8, we approached the logo redesign with a few key goals on mind. 1. We wanted the new logo to be both modern and classic by echoing the International Typographic Style (or Swiss design) that has been a great influence on our Metro style design philosophy. Using bold flat colors and clean lines and shapes, the new logo has the characteristics of way-finding design systems seen in airports and subways. 2. It was important that the new logo carries our Metro principle of being “Authentically Digital”. By that, we mean it does not try to emulate faux-industrial design characteristics such as materiality (glass, wood, plastic, etc.). It has motion – aligning with the fast and fluid style you’ll find throughout Windows 8. 3. Our final goal was for the new logo to be humble, yet confident. Welcoming you in with a slight tilt in perspective and when you change your color, the logo changes to reflect you. It is a “Personal” Computer after all. We hope you enjoy our new logo. via > http://windowsteamblog.com/windows/b/bloggingwindows/archive/2012/02/17/redesigning-the-windows-logo.aspx
  3. attach your scanstate.log and loadstate.log files here (as attachments) and i'll take a look
  4. enable troubleshooting in USMT like I describe here, then review the logs and see what they tell you about your problem - start with scanstate.log see what it tells you it's migrating (or not) http://myitforum.com/cs2/blogs/nbrady/archive/2012/01/25/troubleshooting-usmt.aspx
  5. This is a good question so I've modified your original topic to make it more descriptive and i'm pinning this. Recommended reading:- Site System Requirements:- Technet Note that you cannot enable PXE or Multicast support on your Windows 7 Distribution Point. To troubleshoot your distribution point creation on the Windows 7 box, on your ConfigMgr site server, what does the distrmgr.log file tell you about the problem, if it's complaining about being unable to connect, then you could have firewall issues and/or wmi problems related to the fact that you have a firewall in place and/or IIS is not installed on the Windows 7 computer or doesn't have the following IIS features installed: * IIS 6 WMI compatibility Feature * IIS 6 Management compatibility feature so verify the firewall settings, and then verify that you installed IIS on the Windows 7 computer.. Next verify that you added the ConfigMgr site server computer account to the Local Administrators group on the windows 7 box. The screenshot below is from the Windows 7 computer. Once you've added the account to the Local Administrators group, Note: You must reboot the Windows 7 box before installing the DP role otherwise IIS may not get installed automatically. Installing the Distribution Point Role To start the installation of the Distribution Point role on the Windows 7 box, select Servers and Site System Roles from Site Configuration in the in the Administration part of the ConfigMgr Console. In the Ribbon, click on Create Site System Server, when the wizard appears, type in the FQDN of your Windows 7 computer and select your site code that it will be connected to from the drop down menu. For Site System Installation account you have the option of specifying a service account or the site server computer account, whichever one you use must be a member of the Local Administrators group on your Windows 7 computer. Click Next Select Distribution Point from the list of available roles specify if you want IIS installed automatically or not (Install and configure IIS if required by Configuration Manager) specify drive settings... Do NOT enable PXE support (as this is a Windows 7 box and Windows Deployment Services is not available on Windows 7), just click Next Do NOT enable Multicast (as above) If you want to validate content on a schedule select the box, otherwise click next click next, then for Specify the Boundary Groups to associate with this Site System, click Add and select your boundary from those listed click next through to completion of the Wizard. Monitoring the Distribution Point Role Installation to see how your distribution point installation is progressing, you can monitor it in the ConfigMgr console, check the Distribution Point Configuration Status in Monitoring. Click on the machine name, then select the Details tab underneath, what does it say for your Windows 7 machine, you can even click on More Details in the ribbon to see if it provides more details about your issue. once it's done installing the Distribution Point role you'll see it reports it successfully and creates the needed folder structure on your windows 7 box. if you forgot to install IIS then install it on your Windows 7 box (you don't need to reinstall the distribution point role) once again, monitor the status of your dp again, it should refresh to all Green (ok) and finally, it's all done and working and content is being copied to your new distribution point.
  6. you need to use unconditional excludes like in this example
  7. did you add the computer you are interesting in testing to the collection where you advertised a task sequence ? does that client have a working configuration manager client ?
  8. if you want to migrate registry keys from one location to another (provided that they are detected) then use the following code in a custom XML file <?xml version="1.0" encoding="UTF-8"?> <migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/WNB_move_reg_keys"> <!-- WNB_move_reg_keys.xml is basically a customized version of MigUser.xml --> <_locDefinition> <_locDefault _loc="locNone"></_locDefault> <_locTag _loc="locData">displayName</_locTag> </_locDefinition> <!-- This component migrates Old Reg Keys and moves them to NEW locations provided that the key exists --> <component context="User" type="Application"> <displayName _locID="regkeymove_user">Move old reg keys to new location</displayName> <role role="Settings"> <detects> <detect> <condition>MigXmlHelper.DoesObjectExist("Registry","HKLM\SOFTWARE\CUSTOM [CUSTOMval#1]")</condition> </detect> </detects> <rules> <include> <objectSet> <pattern type="Registry">HKLM\SOFTWARE\CUSTOM [CUSTOMval#1]</pattern> <pattern type="Registry">HKLM\SOFTWARE\CUSTOM [CUSTOMval#2]</pattern> </objectSet> </include> <locationModify script="MigXmlHelper.ExactMove('HKLM\SOFTWARE\CUSTOM [PrevCUSTOMval#1]')"> <objectSet> <pattern type="Registry">HKLM\SOFTWARE\CUSTOM [CUSTOMval#1]</pattern> </objectSet> </locationModify> <locationModify script="MigXmlHelper.ExactMove('HKLM\SOFTWARE\CUSTOM [PrevCUSTOMval#2]')"> <objectSet> <pattern type="Registry">HKLM\SOFTWARE\CUSTOM [CUSTOMval#2]</pattern> </objectSet> </locationModify> </rules> </role> </component> </migration> this code checks if the following registry key exists HKLM\SOFTWARE\CUSTOM\CUSTOMval#1 and if it does, it migrates the following two registry keys from the SOURCE pc HKLM\SOFTWARE\CUSTOM\CUSTOMval#1 HKLM\SOFTWARE\CUSTOM\CUSTOMval#2 to the following locations on the DESTINATION pc HKLM\SOFTWARE\CUSTOM\PrevCUSTOMval#1 HKLM\SOFTWARE\CUSTOM\PrevCUSTOMval#2 Note: if you are using a 64 bit OS with a 32bit application (X86) that you'll probably want to change the path statements for example, change HKLM\SOFTWARE\CUSTOM [CUSTOMval#1] to HKLM\SOFTWARE\Wow6432Node\CUSTOM\ [CUSTOMval#1] cheers niall
  9. another quick USMT post, if you want to avoid your Pinned items (for example Microsoft Office Outlook) from being migrated in a Win7 to Win7 migration, then include the following in a custom XML file as explained in this post, why do you want to do this, well if you don't you just might see Microsoft Office Outlook 2007 (2) as your pinned item name (for example) in the taskbar. <component type="Documents" context="user"> <displayName _locID="miguser.User_Exclusions">User Exclusions</displayName> <role role="Data"> <rules> <unconditionalExclude> <objectSet> <!-- exclude items pinned on the taskbar otherwise it'll cause the same items to show up as (2) desktop--> <pattern type="File">%APPDATA%\Microsoft\Internet Explorer\Quick Launch\User Pinned\TaskBar\* [*.lnk]</pattern> </objectSet> </unconditionalExclude> </rules> </role> </component> and that's probably a good idea looking at my current Windows 7 taskbar the following items are pinned cheers niall
  10. when doing a Refresh from Windows 7 to Windows 7 you may have programs installed on the source computer which are not installed on the destination even if it's the same computer, and as a result you don't want to migrate those unusable shortcuts in the start menu, here's how you can exclude them and in addition exclude some additional items like files on the desktop (msi/exe) or desktop shortcuts. create a custom XML file which you will use in addition to the default USMT xml files that are provided with USMT. copy the below content into this blank XML file save the file as WNB.XML <?xml version="1.0" encoding="UTF-8"?> <migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/WNB"> <!--WNB.xml is basically a customized version of MigUser.xml --> <!-- This component EXCLUDES the following User specific stuff--> <component type="System" context="user"> <displayName _locID="miguser.User_Exclusions">User Exclusions</displayName> <role role="Data"> <rules> <unconditionalExclude> <objectSet> <!-- exclude blank links on the desktop--> <pattern type="File">%CSIDL_DESKTOP%\* [*.msi]</pattern> <pattern type="File">%CSIDL_DESKTOP%\* [*.exe]</pattern> <pattern type="File">%CSIDL_DESKTOP%\* [*.lnk]</pattern> <pattern type="File">%CSIDL_DESKTOP%\* [*.lnk2]</pattern> <pattern type="File">%CSIDL_DESKTOPDIRECTORY%\* [*.msi]</pattern> <pattern type="File">%CSIDL_DESKTOPDIRECTORY%\* [*.exe]</pattern> <pattern type="File">%CSIDL_DESKTOPDIRECTORY%\* [*.lnk]</pattern> <pattern type="File">%CSIDL_DESKTOPDIRECTORY%\* [*.lnk2]</pattern> <pattern type="File">%CSIDL_DEFAULT_DESKTOP%\* [*.msi]</pattern> <pattern type="File">%CSIDL_DEFAULT_DESKTOP%\* [*.exe]</pattern> <pattern type="File">%CSIDL_DEFAULT_DESKTOP%\* [*.lnk]</pattern> <pattern type="File">%CSIDL_DEFAULT_DESKTOP%\* [*.lnk2]</pattern> <pattern type="File">%CSIDL_DEFAULT_PROGRAMS%\* [*]</pattern> <pattern type="File">%CSIDL_DEFAULT_STARTMENU%\* [*]</pattern> <pattern type="File">%CSIDL_DEFAULT_STARTUP%\* [*]</pattern> <pattern type="File">%CSIDL_PROGRAMS%\* [*]</pattern> <pattern type="File">%CSIDL_STARTMENU%\* [*]</pattern> <pattern type="File">%CSIDL_STARTUP%\* [*]</pattern> </objectSet> </unconditionalExclude> </rules> </role> </component> <!-- This component EXCLUDES the following shared User specific stuff--> <component type="System" context="System"> <displayName _locID="miguser.Shared_User_Exclusions">Shared User Exclusions</displayName> <role role="Data"> <rules> <unconditionalExclude> <objectSet> <pattern type="File">%CSIDL_COMMON_DESKTOPDIRECTORY%\* [*.msi]</pattern> <pattern type="File">%CSIDL_COMMON_DESKTOPDIRECTORY%\* [*.exe]</pattern> <pattern type="File">%CSIDL_COMMON_DESKTOPDIRECTORY%\* [*.lnk]</pattern> <pattern type="File">%CSIDL_COMMON_DESKTOPDIRECTORY%\* [*.lnk2]</pattern> <pattern type="File">%CSIDL_COMMON_PROGRAMS%\* [*]</pattern> <pattern type="File">%CSIDL_COMMON_STARTMENU%\* [*]</pattern> <pattern type="File">%CSIDL_COMMON_STARTUP%\* [*]</pattern> <pattern type="File">%CSIDL_PROGRAMS%\* [*]</pattern> <pattern type="File">%CSIDL_STARTMENU%\* [*]</pattern> <pattern type="File">%CSIDL_STARTUP%\* [*]</pattern> </objectSet> </unconditionalExclude> </rules> </role> </component> </migration> wnb.xml to use the file above, simply specify it in your Capture User State and Restore user State steps or manually specify it using i:\wnb.xml for example as below:- C:\USMT\USMT\x64\scanstate.exe C:\USMTStores\OLD_COMPUTERNAME /c /o /nocompress /uel:30 /i:C:\USMT\USMT\x64\WNB.xml /i:C:\USMT\USMT\x64\MigApp.xml /i:C:\USMT\USMT\x64\MigUser.xml /config:C:\USMT\USMT\x64\Windows7_Config.xml /v:13 /l:C:\Windows\temp\scanstate.log /progress:C:\Windows\temp\scanstate_progress.log
  11. i personally woudlnt re-invent the wheel, too much work, the functionality is there in the MDT scripts, which you have access to so if you dont want to create an MDT task sequence dont, but you need to still reference the MDT toolkit package in order to use the scripts.
  12. well integrating MDT with configmgr will make your job much easier, please try it (in a lab) and you'll see what i mean
  13. have you seen my post here ? http://www.windows-noob.com/forums/index.php?/topic/3251-customising-windows-7-deployments-part-4/
  14. target the application deployments to a collection which Excludes Windows XP computers - done.
  15. go ahead and try, and report back your findings here.
  16. you could try programming it but why bother, the supported method of migrating from SMS 2003 to Configuration Manager 2012 is to migrate from SMS 2003 > ConfigMgr 2007 and then do a side-by-side migration to ConfigMgr 2012.
  17. well all the R3 powermanagement features in ConfigMgr 2007 are present in ConfigMgr 2012, have you looked into collection properties theres a Power Management tab, you can select a power management scheme and customise it to turn off things after certain time limits
  18. have you tried using the build and capture task sequence method ? i detail it here in this powerpoint (look at the slide notes), here's the build and capture method in detail Using SCCM 2007 Sp2 to deploy Windows 7 Deploy 7 (4 parts)
  19. hi have you added any filenames to Software Metering, browse to one of the EXE's for an Adobe product, if you want to meter a specific version then add it there ?
  20. there are no more beta 2 parts coming as Release Candidate 2 is already out, look at those guides here
  21. what are you trying to deploy exactly ?
  22. yes you will have problems unless you are a Microsoft TAP customer, you should not install RC2 into production otherwise, it's not supported to upgrade it at all. So you'll have to install again from scratch when the final code is available (RTM).
  23. to remove an update or updates from a software Update Group, you need to select your software update group and right click on an update that you want to remove, select Edit Membership if the update(s) is/are in one or more software update groups then they will be listed here, simply remove the checkmark(s) from the software update group(s) that you want to delete the update from
  24. did you verify what the possible causes were ?, for example the firewall settings ?
  25. well the log will be on the client, did you look there?
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.