We have a solution running on some 140vms in an Azure VMSS.
How do I enable any of these memory dump options through the ARM Template?
Barring that, how could I enable it with a PowerShell script?
I have a new Windows Phone 7 phone, and I'm trying to investigate how to connect the Office application to our SharePoint site(s).
In the Office application, on Phone 7, I flip to the SharePoint page. I go to open URL, and enter the url for one of my sites, that uses default authentication (Windows Auth). I get a message: Can't open SharePoint doesn't support this authentication scheme. For assistance, contact the person who manages thus SharePoint site (That would be me). You can try opening the content in your web browser instead.
When opening in my browser, I can access the content without any problem. (Windows Auth passes)
Anyone have any source material on what I should do to my SharePoint site to "support this authentication scheme?"
Note: I am the administrator of our SharePoint server farm(s).
When trying to extend an existing SharePoint 2010 web application, I get an error. The Web App is running Claims Authentication. I disabled NTLM Auth on the Default Zone - we want the public (default) zone to be Claims / FBA only. We need to expand the web app to make a new zone to enable Search (requires NTLM Auth).
ERROR: System.FormatException: Input string was not in a correct format. at System.Number.StringToNumber (String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) at Microsoft.SharePoint.Administration.SPIisWebSite.Lookup(Uri uri, Boolean requireHighMatchLevel, Int32& instanceId) at Microsoft.SharePoint.Administration.SPProvisioningAssistant.StopSitesWithMatchingBindings(SPIisSettings settings) at Microsoft.SharePoint.Administration.SPProvisioningAssistant.ProvisionWebApplication(String webApplicationName, String applicationPoolName, SPIisSettings[] settings, Boolean adminWebApp) at Microsoft.SharePoint.Administration.SPWebApplication.ProvisionIisWebSi... 8da4ec82-1802-48c3-b595-21a968db9718 06/29/2010 13:24:27.32* w3wp.exe (0x103C) 0x1364 SharePoint Foundation Runtime tkau Unexpected ...tesAsAdministrator() at Microsoft.SharePoint.Administration.SPWebApplication.ProvisionIisWebSites() at Microsoft.SharePoint.Administration.SPWebApplication.Provision() at Microsoft.SharePoint.ApplicationPages.ExtendWebFarmPage.BtnSubmit_Click(Object sender, EventArgs e) at System.Web.UI.WebControls.Button.OnClick(EventArgs e) at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 8da4ec82-1802-48c3-b595-21a968db9718
I have an existing FBA database of ~2000 users for one of my clients in WSS 3.0.
I have successfully upgraded their WSS site collection (in a test environment) to SharePoint 2010.
I have also configured the 2010 installation to use FBA (through Claims Based Authentication) and verified that the users can be seen from the site collection.
The problem arrises in the way that the Security Token Service (STS) hands user info to SharePoint compared to the old way; the user token from STS does not match the format of the users that already exist in the site collection and they get "Access Denied."
For instance, In the Site Collection, the user EtherDragon is referred to as "fbamembership:etherdragon" However, the STS refers to me as "0.f|fbamembership|etherdragon" which has no perms.
Is there an good way to either get STS to use the old format or map current site collection users to their STS equivalent?
What I would like to avoid, if possible, is having to remove and re-add ~2000 users from their groups in SharePoint.
I would like to know if there is a (cost free) way to backup Windows Server 2008 Active Directory and DNS settings without using Windows Server Backup.
The problem stems from not having a seperate volume available to store the resulting backup from Windows Server Backup.
I examined the command line options with wbadmin and it also expects the destination to be a dedicated volume for the backup.
~ED