pc3000
asked on
deployment considerations for Office 2007 and Instant Search in Terminal Services
Currently running Exchange and Outlook 2003. We run Terminal Services that remote users access via RDP.
I'm thinking about deploying Office 2007 on the Terminal Server to give remote users the benefits of Instant Search for their emails.
1. Are there any planning/deployment issues I should be aware of? Is Instant Search within Outlook even supported in a Terminal Services environment?
2. The volume on the server that houses the user profiles is running low on space. Do the indexes created by Instant Search take up a lot of space? Do I have the ability to change the location where they're stored to a different drive?
Thanks!
I'm thinking about deploying Office 2007 on the Terminal Server to give remote users the benefits of Instant Search for their emails.
1. Are there any planning/deployment issues I should be aware of? Is Instant Search within Outlook even supported in a Terminal Services environment?
2. The volume on the server that houses the user profiles is running low on space. Do the indexes created by Instant Search take up a lot of space? Do I have the ability to change the location where they're stored to a different drive?
Thanks!
ASKER
Kind of answering my own question here...
Since Outlook installed in Terminal Services does not allow for Cached Mode, that means that Instant Search is going to be looking to the indexes on the Exchange server itself to pull results.
We're running Exchange 2003. So now the question becomes, will we only be able to utilize Instant Search in this environment by upgrading to Exchange Server 2007?
Or can Outlook 2007's Instant Search pull server index results from an Exchange 2003 server. Sounds like a whole mess of potential performance problems...hmm.
Since Outlook installed in Terminal Services does not allow for Cached Mode, that means that Instant Search is going to be looking to the indexes on the Exchange server itself to pull results.
We're running Exchange 2003. So now the question becomes, will we only be able to utilize Instant Search in this environment by upgrading to Exchange Server 2007?
Or can Outlook 2007's Instant Search pull server index results from an Exchange 2003 server. Sounds like a whole mess of potential performance problems...hmm.
Instant search also works with Exchange Server 2003.
As long as your terminal server meets the min. req. for 2007 you should be fine.
However, personally I would not install or upgrade to Office 2007 w/ Instant Search 4.0 on TS just to allow users to use Instant Search.
If you already have Outlook 2003 with the latest SP installed users should be able to utilize the advanced search within Outlook.
Additionally, In my opinion, Search Options within Outlook do not get used enough to justify an upgrade to 2007 w/instant search.
If it aint broke, dont fix it.
As long as your terminal server meets the min. req. for 2007 you should be fine.
However, personally I would not install or upgrade to Office 2007 w/ Instant Search 4.0 on TS just to allow users to use Instant Search.
If you already have Outlook 2003 with the latest SP installed users should be able to utilize the advanced search within Outlook.
Additionally, In my opinion, Search Options within Outlook do not get used enough to justify an upgrade to 2007 w/instant search.
If it aint broke, dont fix it.
ASKER
Well, upgrading to 2007 on the TS is in the works anyway...instant search is not the sole reason. As more people get 2007 on their desktops, they're coming to like and expect the new interface. Plus the instant search frame is better integrated in 2007. 2003's advanced find just seems clunky by comparison.
But back to the nuts and bolts...in an uncached outlook environment, how does instant search pull its results from the 2003 exchange server? Does full-text indexing need to be enabled?
But back to the nuts and bolts...in an uncached outlook environment, how does instant search pull its results from the 2003 exchange server? Does full-text indexing need to be enabled?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Got it...that Group Policy setting is the key -- allowing it to index uncached emails. Looks like GP also lets you specify a location of the index too.
Found some fourm threads that are more on point with running WDS in a TS environment:
http://social.msdn.microsoft.com/Forums/en-US/windowsdesktopsearchhelp/thread/b2329555-ad0c-46ee-9f97-c7f4538e26a5/
http://social.msdn.microsoft.com/forums/en-US/windowsdesktopsearchhelp/thread/791df90c-1471-4c5e-ac95-443c5998e919/
Found some fourm threads that are more on point with running WDS in a TS environment:
http://social.msdn.microsoft.com/Forums/en-US/windowsdesktopsearchhelp/thread/b2329555-ad0c-46ee-9f97-c7f4538e26a5/
http://social.msdn.microsoft.com/forums/en-US/windowsdesktopsearchhelp/thread/791df90c-1471-4c5e-ac95-443c5998e919/
Glad your on to it now.
However, I believe the full amount with a "B" Grade is more fair.
What's the right grade to give?
Grading at Experts Exchange is not like school. It's more like the "10-point Must" system in professional boxing; in other words, an answer is worth an A, unless it doesn't resolve your issue. If it requires you to do a little more research, or figure out one more piece of code, then it's worth a B. If you think it's not worth a B, the custom is to offer the Experts an opportunity to earn a better grade.
However, I believe the full amount with a "B" Grade is more fair.
What's the right grade to give?
Grading at Experts Exchange is not like school. It's more like the "10-point Must" system in professional boxing; in other words, an answer is worth an A, unless it doesn't resolve your issue. If it requires you to do a little more research, or figure out one more piece of code, then it's worth a B. If you think it's not worth a B, the custom is to offer the Experts an opportunity to earn a better grade.
ASKER
Sure. Changing to 500.
ASKER
http://technet.microsoft.com/en-us/magazine/2008.02.officets.aspx