This message was deleted.
# microsoft-fslogix
s
This message was deleted.
n
Yeah, that's kinda what I figured. I only thought about it to address a random crashing issue that I can't narrow down.
t
We run 64bit without any problems. Should probably at least test 32bit one of these days
n
If we ever migrate to O365, that'll be 64-bit.
w
I use 64bit for loading massive Word and Excel files
p
Understand your applications and especially any plugins that are used in the environment.
⤴️ 1
d
on 64bit for a couple of years now and working well, of course it depends on your addons zoo
⤴️ 2
n
Zero custom add-ons here, just the standard Exchange nonsense.
j
All depends on requirements
p
If you do decide to go the 64 bit route in general, test, test, test with actual users. Try to get an inventory/audit, talk to a subset of users. Often people don’t know what random plugins are in use and those aren’t always captured or known of by IT in general
⤴️ 1
Move it in with a phased approach
⤴️ 1
l
As it's been said, plugins are pretty much key.
👍 1
n
I'm going to spend all day tomorrow in a session trying to get it to bomb with ProcMon running. It was crashing even with add-ons disabled.
a
Microsoft is now recommending 64-bit as the default.
n
Saw that earlier. I'm building an Office 2016 x64 App Layer to test out right now. The two guys I know seeing this are both in IS, and have been good about using QA images while I work on things.