I started to do the switch and found that Office was still 32 bit, there may have been other issues but that was the biggest one on the test machine I had. I had a graphics system that was scheduled to remain an x32 XP system due to software licensing issues so the Web developer could have migrated any of his apps to it without issue.
Jon On Thu, Jan 21, 2010 at 11:09 AM, Glen Johnson <gjohn...@vhcc.edu> wrote: > Humm. Change one gp setting, break maybe one or two apps. > Switch 200+ computers to 64bit, and break who knows what? > I think we have a differing definition of "easier". > > Just for fun, have any of you folks switched an org to 64? > If so, what kinds of problems did you face? > > -----Original Message----- > From: Terry Dickson [mailto:te...@treasurer.state.ks.us] > Sent: Thursday, January 21, 2010 10:21 AM > To: NT System Admin Issues > Subject: RE: 16 bit VDM > > There is an easier solution just switch all user to 64 Bit OS and > problem solved. > > -----Original Message----- > From: Glen Johnson [mailto:gjohn...@vhcc.edu] > Sent: Thursday, January 21, 2010 7:48 AM > To: NT System Admin Issues > Subject: 16 bit VDM > > Anyone implemented the group policy mentioned in this article? > > If so, did you see any side effects. > > I don't know of any old 16 bit programs that are in use here, but I > guess there could be some we aren't aware of. > > http://www.h-online.com/security/news/item/Windows-hole-discovered-after > -17-years-Update-908917.html > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
