Unconfigured Ad Widget

Collapse

Enterprise conversion from XP to Win7

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • meaty-btz
    replied
    Originally posted by NytWolf
    Most vb script macros created in Office 2003 will run in Office 2010, which is better than 2007. Those that don't run will need to be recreated.

    I wouldn't recommend running programs in XP compatibility mode. Why even upgrade to Win7 then? Also, I do not recommend going to 64-bit Win7 unless you absolutely have to. Most applications that exist are still 32-bit anyway. Not only will they run faster in the 32-bit OS, you won't have to resort to the compatibility mode.
    WAT? (yes spell correctly)

    You have no idea how x64 vs x32 operates in an Enterprise Environment. The only time x32 is an advantage is when hacking older drivers to force them to be used by windows 7 and said drivers were only available in 32-bit (xp and early vista) . This is NOT a good thing to do in the first place and any hardware that requires such should be retired by any sane enterprise. No 32bit programs run faster on x32 vs x64 versions of windows because x64 has full compatibility with 32-bit libraries and therefor programs. In fact many newer enterprise software IS 64-bit.


    You should have a migration roadmap. If you don't make one. It should include the companies normal hardware cycle (usually 36months) and should be situated on said cycle in such a way as to retire old and incompatible hardware in such a way as to ease migration.

    If you want more from me you are going to be paying me $$ for that information. Not to be harsh but what I have learned migrating over 100 servers, our domain, our exchange server, our virtual machines, our VDI, our 6000 desktops over to windows 7 was hard earned and worth its weight in gold.

    Leave a comment:


  • odysseus
    replied
    Curious, when you say "enterprise", how large are we talking? How many systems and users?

    Leave a comment:


  • NytWolf
    replied
    Most vb script macros created in Office 2003 will run in Office 2010, which is better than 2007. Those that don't run will need to be recreated.

    I wouldn't recommend running programs in XP compatibility mode. Why even upgrade to Win7 then? Also, I do not recommend going to 64-bit Win7 unless you absolutely have to. Most applications that exist are still 32-bit anyway. Not only will they run faster in the 32-bit OS, you won't have to resort to the compatibility mode.

    Leave a comment:


  • Montu
    replied
    I've also noticed the VBA script issue

    Leave a comment:


  • SouperMan
    replied
    Are you planning to go 64-bit Windows 7 and/or 64-bit Office 2010?

    I noticed that a lot of custom built VBA scripts and some Access Databases would not run until I recompiled it in Office 2010.

    If you are super concerned about Office compatibility, you may use Windows XP Mode which will create a virtual instance of Windows XP
    and install apps that won't work in Win7.

    Sent from my mobile using Tapatalk

    Leave a comment:


  • Diabolus
    started a topic Enterprise conversion from XP to Win7

    Enterprise conversion from XP to Win7

    I know many of you are in the IT world and I am in need of some help.

    I'm trying to better understand the pain points when migrating from XP to Win7, including an upgrade from Office 2003 to Office 2010.

    I'm looking more from the end-user perspective, and any issues the end-user would experience on the new Win7 and Office 2010.

    I'm concerned with everything, including issues with converting Excel 2003 to 2010, especially so with macros.

    Any help, resources, or your experience would be a massive help.

    Thanks
Working...
UA-8071174-1