Showing page 1 of 4 (38 total posts)
< 1 second(s)
Mike, would be very interested to hear how your DR test goes, and also some more information on the farm, user count and DR technique.
I hear that Axceler, the guys who do ControlPoint, are hoping to be there, so this might hit some of your backup questions.
You should bone up so that you can get some good questions going on. :o)
Sorry, what part is not the case, and what part is dangerous?
For true audit on the DB layer table or cube, you need to know the credentials of the person accessing, when they accessed, what they accessed and whether they received the requested information.
With out passing through the credentials and confirming that they are authenticated, how ...
I guess the quickest way, with out anyone stepping up and naming the exact component, is to take a copy of the original results.aspx and fiddle around with it till you find the component. There's only a couple in the area so shouldn't take long... ;o)
Sorry yes, I should also second Dean Cassell, spoke with him many times of the last couple of years. Sorry about that! :o)
Be careful with that!
The fact that someone is trying to expose data or content through this method usually implies that, perhaps, there is a touch of compliance, so it should be explained that if no audit trail on the data sources is required, then yes, Spencer is correct, otherwise, if audit is required on the data source, then I'm afraid that ...
You're in a difficult place at the moment.
On the main agencies, Pathway/Progressive, there's been a recent shift in the last 12 months when their SharePoint 'specialists' have all left.
Square 1 has Chris Parsons, he's been around the block a bit so knows what's what.
Glenn Norris, ex Pathway, seems to know his stuff and is now at ...
Isn't the issue with federated search that the search results are not properly stacked together? Wouldn't it be better to have the search center and indexer located on the main farm, indexing both farms. You would then need to re-direct the small farm to the large farm for queries using the search center config to enter the main search center URL.
Hi there, I've seen this problem in the following examples:
SharePoint hosted on VMWare servers using Kerberos where the VM clocks were out of sync with the DC, meaning the Kerberos tickets were expiring mid-session and a new one being issued, forcing SharePoint to think you were a new session, hence the page being modified since last ...
stsadm is the way to go then:
The link above should help get your head around what needs to be done, and well worth book-marking