Reputation
597
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
1 6 25
Impact
~102k people reached

  • 0 posts edited
  • 1 helpful flag
  • 47 votes cast
May
4
comment Getting 401 error when connecting to the list.asmx web service using JQUERY
could be some kind of transparent proxy in play as well, or a proxy that is modifying the auth messages. I see the site is using NTLM
Apr
30
comment UserProfile Not Running - am I setting myself up for a fall?
I think I was more concerned with if new users were going to end up having an issue with not seeing their display name properly when authenticating against the site, the customer isn't really using the features discussed thankfully. The only thing complained about was My Links after the 2007 to 2010 migration - but thats been deprecated anyway.
Apr
27
answered Claim SQL server space after content deleted from SharePoint
Apr
27
asked UserProfile Not Running - am I setting myself up for a fall?
Apr
27
answered User Profile Synchronization won't start
Apr
27
answered Add Application Server to existing SharePoint farm - production hours
Apr
27
asked Change installation directory of a SharePoint 2007 post install
Apr
24
answered problem restoring sharepoint from backup
Apr
24
answered Sharepoint Server 2010 development environment setup error
Apr
20
comment User Profile Application - MOSS MA not found
Unsure on the reference link?, but thanks for the lead. There could possibly be some service level blocking in effect on the server for sure, I've managed to get the site admins to pull any kind of proxy enforcement from the SharePoint server so I can probably remove that from the equation now.. but its still an issue
Apr
17
comment SharePoint 2007 -> 2010 upgrade content database size currently over 100GB
Well this site has now lost their WFE, oh the joy. Looks like I'll be doing a restore using databases only..
Apr
17
asked User Profile Application - MOSS MA not found
Apr
5
comment SharePoint 2007 -> 2010 upgrade content database size currently over 100GB
Thanks for the reply Bas, as it stands the current DB server has run out of space so trying to remove sites / document librarys will no doubt blow the log files out and I'll run out of space. My thoughts are to detach / attach the current 165GB DB then bring it down. Due to the solutions installed on the farm my only option is to do an inplace upgrade which I have a process for and have done on 20 other SharePoint 2007 farms so I know a trick or 2 about how to get that to work.
Apr
4
comment Splitting a Content Database into two or three?
I guess this works provided you have your content split up into manageable site collections but if you've got a really large site collection then you're pretty much out of luck?
Apr
4
asked SharePoint 2007 -> 2010 upgrade content database size currently over 100GB
Mar
15
accepted WSS 3.0 2 servers consolidation options
Mar
15
answered WSS 3.0 2 servers consolidation options
Mar
12
asked WSS 3.0 2 servers consolidation options
Feb
24
comment Editing default master Broke Central Admin
you wouldn't by any chance have the publishing feature enabled and be able to restore an earlier version? Also you mention you're working on a 2010 install, I would have thought that you would have been working with v4.master
Feb
24
accepted Additional WFE 401 errors?