MDT 2013 and locationserver.xml prompting for credentials

I have multiple locations we are sharing our DeploymentShare so we are using a LocationServer.xml file to pull from one of those locations. We have everything working except that we can not get rid of the credentials prompts.
Does anyone have a solution for that ?
Thanks
Don

Hi,
Have you replicated all the system folders in the Public Folder to the Exchange 2013 server, especially for the EFORMS REGISTRY folder since the Outlook will try to access this
folder when loading and Organization Forms templates.
Happy New Year!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Similar Messages

Shared folders (Windows file shares) show access denied and do not prompt for credentials

Scenario:
Like other admins, I log on and work as a 'standard user' (usera) with no admin rights anywhere in the domain, to perform admin tasks I have another account (userb) which I authenticate with as and when required. userb has been allocated/delegated permissions
as required.
Problem:
When trying to connect to shared folders on servers (2008 R2) using a UNC patch via Windows Explorer (Win 7 Ent.), I see an access denied error and do not get an option to supply alternative credentials.
If I try to connect to the admin shares on the same server (\\server\C$ or \\server\e$) I get an access denied message AND get prompted for credentials. I supply my admin account and gain access as expected.
If I check share and storage management when attempting to connect, I see that Windows is trying to connect me to each share as usera (which has no access). I understand why I get access denied at this point, but not why it can't just prompt me to supply an
account that does have access. When trying the admin shares I also see the usera account, but I get a prompt to supply a user who does have access.
Share permissions on the folders are for example 'Everyone' Full Control. NTFS permissions are 'userb' has modify (read, execute, list, traverse etc) via a 'Server Admins' AD Universal security group.
Note: If I do a NET USE from CMD and use the /USER switch, I can access the shares fine. But this is not great for accessing shared folders on the fly from various computers.
How can I get the other shares on the server to prompt me, rather than just say access denied?
Many thanks.

Try to disable guest user from the server
If you found this post helpful, please give it a "Helpful" vote. If it answered your question, remember to mark it as an "Answer". This posting is provided "AS IS" with no warranties and confers no rights! Always test ANY
suggestion in a test environment before implementing!

Exchange 2007 to 2013 Migration issues. Prompt for credentials, Public Folders inaccessible, Apps not working

Exchange 2013 Migration issues
I have three issues and decided to list them here. Please pick and choose to assist. Thanks in advance.
Environment:
Mixed 2007 SP3 R12 and 2013 CU3. 2007 Environment was webmail.domain.com. I installed new Exchange 2013 (1 CAS, 1 Mailbox) according to:
http://technet.microsoft.com/en-us/library/ff805032(v=exchg.150).aspx. Exchange 2007 is now legacy.domain.com and Exchange 2013 CAS is webmail.domain.com.
Machine 1: Windows 8.1, not domain joined, using Outlook Anywhere external. Outlook 2013
Machine 2: Windows 7, domain joined, using Outlook Anywhere internal. Outlook 2010 SP2
I have migrated 1 user so far to Exchange 2013. This user was a Domain Admin. I have removed that membership. I checked the box to inherit permissions of the security of the object and reset the AdminCount attribute in ADSIedit to 0 and verified this replicated
to all domain controllers. ( I originally thought this to be the issue with it prompting for the password. )
Here is a Get-OutlookAnywhere cmdlet...
ServerName                         : EXCHANGE2007SVR
SSLOffloading                      : False
ExternalHostname                   : legacy.domain.com
InternalHostname                   :
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Basic
IISAuthenticationMethods           : {Basic}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : False
MetabasePath                       : IIS://EXCHANGE2007SVR.domain.local/W3SVC/1/ROOT/Rpc
Path                               : C:\WINDOWS\System32\RpcProxy
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 8.3 (Build 83.6)
Server                             :
EXCHANGE2007SVR
AdminDisplayName                   :
ExchangeVersion                    : 0.1 (8.0.535.0)
Name                               : Rpc (Default Web Site)
DistinguishedName                  : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=EXCHANGE2007SVR,CN=Servers,CN=Exchange
                                     Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
                                     Groups,CN=DOMAIN,CN=Microsoft
                                     Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=local
Identity                           : EXCHANGE2007SVR\Rpc (Default Web Site)
Guid                               : 4901bb14-ab81-4ded-8bab-d5ee57785416
ObjectCategory                     : domain.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged                        : 12/31/2013 4:08:04 PM
WhenCreated                        : 7/18/2008 10:56:46 AM
WhenChangedUTC                     : 12/31/2013 9:08:04 PM
WhenCreatedUTC                     : 7/18/2008 2:56:46 PM
OrganizationId                     :
OriginatingServer                  : DC1.domain.local
IsValid                            : True
ObjectState                        : Changed
ServerName                         :
EXCHANGE2013SVR
SSLOffloading                      : True
ExternalHostname                   : webmail.domain.com
InternalHostname                   : webmail.domain.com
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True
MetabasePath                       : IIS://EXCHANGE2013SVR.domain.local/W3SVC/1/ROOT/Rpc
Path                               : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 15.0 (Build 775.38)
Server                             : EXCHANGE2013SVR
AdminDisplayName                   :
ExchangeVersion                    : 0.20 (15.0.0.0)
Name                               : Rpc (Default Web Site)
DistinguishedName                  : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=EXCHANGE2013SVR,CN=Servers,CN=Exchange
                                     Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
                                     Groups,CN=DOMAIN,CN=Microsoft
                                     Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=local
Identity                           : EXCHANGE2013SVR\Rpc (Default Web Site)
Guid                               : d983a4b1-6921-4a7f-af37-51de4a61b003
ObjectCategory                     : domain.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged                        : 1/7/2014 11:29:05 AM
WhenCreated                        : 12/31/2013 1:17:42 PM
WhenChangedUTC                     : 1/7/2014 4:29:05 PM
WhenCreatedUTC                     : 12/31/2013 6:17:42 PM
OrganizationId                     :
OriginatingServer                  : DC1.domain.local
IsValid                            : True
ObjectState                        : Changed
ISSUE 1
Issue: On Machine 1 (reference above) Windows Security prompt that says "Connecting to
[email protected]". Almost always prompts when Outlook is first opened. Afterwards (if it goes away) seemingly random on when it asks for it. I put in the credentials (absolutely correct) and it fails and prompts again.
I always check the box for it to save the password. To get rid of it, I click the Cancel button at which Outlook reports "NEED PASSWORD", but still acts fine sending and receiving emails. Eventually the "NEED PASSWORD" sometimes changes
to say "CONNECTED", but it works regardless.
No issues on Machine 2 so I don't know where the problem might be as there are a lot of variables in play here.
ISSUE 2
Migrated user is unable to open Public folders from Exchange 2007.
Cannot expan the folder. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance. (/o=...).
This error occurs on Machine 1, Machine 2 and from OWA, same error each time.
ISSUE 3
Apps. Installed by default are 4 apps (Bing Maps, Suggested Meetings, Unsubscribe, Action Items). I have made sure the apps are enabled in OWA and they show up in mail items on both Machine 1 (Outlook 2013) and OWA. They do not show up in Machine 2 (Outlook
2010). I'm assuming that isn't supported.
In OWA, when I go to the installed apps listing it shows all of the apps but has a broken link on the image describing the app.
When I click the app in either Outlook 2013 or in OWA, I get "APP ERROR, Sorry we can't load the app. Please make sure you have network and/or internet connectivity. Click "Retry" once you're back online.
Current workaround is just disabling them through OWA.

Hello,
In order to avoid confusion, we troubleshoot a issue per thread usually.
For your first isue, I agree with Ed's suggestion to check if your certificate name is correct.
Besides, I recommend you change ExternalClientAuthenticationMethod from Basic authentication to Negotiate authentication to check the result.
For the second issue and third issue, please create a new post.
If you have any feedback on our support, please click here
Cara Chen
TechNet Community Support

Outlook 2013 patch of November 12, 2013 makes Outlook repeatedly prompt for credentials

Hi,
Since November 12 Tuesday patch day my Outlook 2013 would repeatedly prompt me for credentials on one of my Exchange account. I reported this to our help desk in charge of mail services and they couldn't explain how this can happen as my mailbox was configured
correctly using Auto Discovery. Deleting and recreating my Outlook profile did not help as didn't further tips found on the net. I could confirm my correct credentials 10 times in a row and the window wouldn't stop popping up immediately again. If I clicked
cancel, the prompts would reappear after a couple of minutes. This can be hugely disruptive to one's productivity.
Since I realized all had been fine since that massive roll out of updates, I began to wonder which update exactly may have caused it. My plan was to uninstall updates of that day one by one and to narrow down the culprit.
My first shot was successful:
Security Update of Microsoft Outlook 2013 (KB2837618) 32-Bit edition
When uninstalling this one, another update is removed automatically:
Update for Microsoft Office 2013 (KB2837643) 32-Bit edition
That was it. Once these guys were removed, there was finally peace again. But beware! If you have automatic Windows Updates enabled, they are quietly streamed back to your computer in a matter of minutes and the infernal prompts start again. Hence, you basically
have to turn automatic updates off and then make sure these get not installed again in future.
At least until Microsoft provides a patch for the patch.
As a sidenote, I should mention that this problem only occurs for one of my 3 Exchange accounts, all with different companies (none is a Microsoft Cloud-based one). So perhaps it is the interaction of that new update AND some faulty server-side settings that
are at the root of the problem, really. As I'm no sys admin, I wouldn't know how to figure it out but leave the clues given here to the experts. Very ironically, I never encountered any problems with any of my Exchange accounts on any of my Mac or iOS clients.
EDIT: In the bugfix description ttp://support.microsoft.com/kb/2837618 they list under known issues: "After this update is applied, you may experience issues with S/MIME certificate verification in Microsoft Outlook. This issue is caused because the update
disables remote intermediate certificate fetching in Outlook." And then they give you a registry hack to apply at your own risk. I do not know how to decipher this, do "issues with S/MIME certificate verification" give rise to the infinite loop
of credential prompts?

With the MS update rollout of 14 January 2014, the new patch to remove manually to maintain normal functionality and not have the above repeated credential prompts is: KB2850061 (Update for Microsoft Outlook 2013), http://support.microsoft.com/kb/2850061
Otherwise, since that day, the prompts kept reappearing on my computer.
Please vote up my posts if you find this information useful.

Outlook 2013 continually prompting for credentials on new domain

Greetings,
I first posted this in the Office365 community forums and was directed here.
We are experiencing an issue where Outlook 2013 (Office365 install) is prompting for user credentials every time it is opened, despite checking the option to remember the credentials. So far we've tried a number of troubleshooting steps, but nothing
has resolved the issue. The issue is happening to multiple users on multiple computers.
We are running:
Outlook 2013 (32-bit) (Office 365 install)
Windows 7.1 Professional (x64)
Computer is domain joined (Server 2012 R2 Domain Controllers)
Mail is hosted on Office 365
We've tried:
Clearing the Outlook and Office credentials from Credential Manager.
Removing the mail profile and the saved credentials from Credential Manager, then re-adding the mail profile.
We've tried adding the mail profile with both a manual configuration of the server settings and allowing Outlook to automatically configure them.
Ensuring that "Always prompt for logon credentials" is unchecked.
Setting "Always prompt for logon credentials" to disabled via registry (see
http://support.microsoft.com/kb/2984912)
Confirming that Autodiscover is able to connect (http://www.microsoft.com/en-us/showcase/details.aspx?uuid=e8db028a-06f4-45fb-aff1-e8ac896d29c5)
Deleting the Autodiscover.xml file so that it is recreated
Doing an Online Repair of Office 365.
Reinstalling Office 365
Recreating the user's Windows profile.
Ensuring all applicable Windows updates and Office updates are installed.
Changing Proxy Authentication from Basic to NTLM (will not connect with NTLM)
The machines this is occurring on are on a new domain that we are in the process of setting up. The user accounts are still on the old domain. Cross-domain trusts are set up in both directions and all other services are working fine. GPO settings across
both domains have been set up to be identical. The issue occurs on computers that were built directly on the new domain as well as computers built on old domain and migrated over. Machines that are not domain joined or are still on the old domain are not experiencing
the issue.
If any of you could provide any insight or other steps that we could try I'd greatly appreciate it.
Thanks

Hi,
For the issue that Outlook keeps prompting for password, I usually suggest users follow the steps in this article below, but apparently you have tried almost all the steps:
Why does Outlook keep prompting for password
I've seen some similar issues that were caused by an old "network driver", which for some reason caused a wrong server name to propagate up from the network layer to the application layer. Updating the network driver would fix the issue, I'm
not sure if this works in your scenario though.
Regards,
Melon Chen
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs. Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Exhcnage 2013 Migration - User keep keeping prompted for credentials

Hello,
I am migrating all on-premise exchange 2010 SP3 to Exchange 2013 SP1. I am testing mailbox migrations, each mailbox that gets moved to 2013 the user keeps getting prompted for credentials. I have read several posts in the forums yet none which solve my problem.
Can someone point me in the right direction. All 2013 setting are currently at default.

Thank you for your help and your quick response.
Here is the autodiscover test. When I move the mailbox to 2013 its picks up the 2013 URL. In this output mail.myserver.com is the hostname of my 2013 cas.
Also noticed the following in the server field under account settings.
<?xml version="1.0" encoding="utf-8"?>
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
    <User>
      <DisplayName>2013test</DisplayName>
      <LegacyDN>/o=mycompany/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=2013test436</LegacyDN>
      <AutoDiscoverSMTPAddress>[email protected]</AutoDiscoverSMTPAddress>
      <DeploymentId>91ce898c-65a0-402e-be70-622d0a31f7c3</DeploymentId>
    </User>
    <Account>
      <AccountType>email</AccountType>
      <Action>settings</Action>
      <MicrosoftOnline>False</MicrosoftOnline>
      <Protocol>
        <Type>EXCH</Type>
        <Server>[email protected]</Server>
        <ServerDN>/o=mycompany/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]</ServerDN>
        <ServerVersion>73C08391</ServerVersion>
        <MdbDN>/o=mycompany/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]/cn=Microsoft Private MDB</MdbDN>
        <PublicFolderServer>mail.myserver.com</PublicFolderServer>
        <AD>nohdomp1.domain.LOCAL</AD>
        <AuthPackage>Anonymous</AuthPackage>
        <ASUrl>https://mail.myserver.com/ews/exchange.asmx</ASUrl>
        <EwsUrl>https://mail.myserver.com/ews/exchange.asmx</EwsUrl>
        <EmwsUrl>https://mail.myserver.com/ews/exchange.asmx</EmwsUrl>
        <EcpUrl>https://mail.myserver.com/ecp/</EcpUrl>
        <EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=domain.LOCAL</EcpUrl-um>
        <EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=domain.LOCAL</EcpUrl-aggr>
        <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=domain.LOCAL</EcpUrl-mt>
        <EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=domain.LOCAL</EcpUrl-ret>
        <EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=domain.LOCAL</EcpUrl-sms>
        <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=domain.LOCAL</EcpUrl-photo>
        <EcpUrl-tm>?rfr=olk&ftr=TeamMailbox&exsvurl=1&realm=domain.LOCAL</EcpUrl-tm>
        <EcpUrl-tmCreating>?rfr=olk&ftr=TeamMailboxCreating&SPUrl=<SPUrl>&Title=<Title>&SPTMAppUrl=<SPTMAppUrl>&exsvurl=1&realm=domain.LOCAL</EcpUrl-tmCreating>
        <EcpUrl-tmEditing>?rfr=olk&ftr=TeamMailboxEditing&Id=<Id>&exsvurl=1&realm=domain.LOCAL</EcpUrl-tmEditing>
        <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=domain.LOCAL</EcpUrl-extinstall>
        <OOFUrl>https://mail.myserver.com/ews/exchange.asmx</OOFUrl>
        <UMUrl>https://mail.myserver.com/ews/UM2007Legacy.asmx</UMUrl>
        <OABUrl>https://mail.myserver.com/OAB/4b0a14e4-d177-415f-9acf-b51b966b6dd8/</OABUrl>
        <ServerExclusiveConnect>off</ServerExclusiveConnect>
      </Protocol>
      <Protocol>
        <Type>EXPR</Type>
        <Server>mail.myserver.com</Server>
        <SSL>On</SSL>
        <AuthPackage>Negotiate</AuthPackage>
        <ASUrl>https://mail.myserver.com/ews/exchange.asmx</ASUrl>
        <EwsUrl>https://mail.myserver.com/ews/exchange.asmx</EwsUrl>
        <EmwsUrl>https://mail.myserver.com/ews/exchange.asmx</EmwsUrl>
        <EcpUrl>https://mail.myserver.com/ecp/</EcpUrl>
        <EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=domain.LOCAL</EcpUrl-um>
        <EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=domain.LOCAL</EcpUrl-aggr>
        <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=domain.LOCAL</EcpUrl-mt>
        <EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=domain.LOCAL</EcpUrl-ret>
        <EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=domain.LOCAL</EcpUrl-sms>
        <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=domain.LOCAL</EcpUrl-photo>
        <EcpUrl-tm>?rfr=olk&ftr=TeamMailbox&exsvurl=1&realm=domain.LOCAL</EcpUrl-tm>
        <EcpUrl-tmCreating>?rfr=olk&ftr=TeamMailboxCreating&SPUrl=<SPUrl>&Title=<Title>&SPTMAppUrl=<SPTMAppUrl>&exsvurl=1&realm=domain.LOCAL</EcpUrl-tmCreating>
        <EcpUrl-tmEditing>?rfr=olk&ftr=TeamMailboxEditing&Id=<Id>&exsvurl=1&realm=domain.LOCAL</EcpUrl-tmEditing>
        <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=domain.LOCAL</EcpUrl-extinstall>
        <OOFUrl>https://mail.myserver.com/ews/exchange.asmx</OOFUrl>
        <UMUrl>https://mail.myserver.com/ews/UM2007Legacy.asmx</UMUrl>
        <OABUrl>https://mail.myserver.com/OAB/4b0a14e4-d177-415f-9acf-b51b966b6dd8/</OABUrl>
        <ServerExclusiveConnect>on</ServerExclusiveConnect>
        <EwsPartnerUrl>https://mail.myserver.com/ews/exchange.asmx</EwsPartnerUrl>
        <GroupingInformation>NebraskaOrthopaedicHospital</GroupingInformation>
      </Protocol>
      <Protocol>
        <Type>WEB</Type>
        <Internal>
          <OWAUrl AuthenticationMethod="Basic, Fba">https://mail.myserver.com/owa/</OWAUrl>
          <Protocol>
            <Type>EXCH</Type>
            <ASUrl>https://mail.myserver.com/ews/exchange.asmx</ASUrl>
          </Protocol>
        </Internal>
        <External>
          <OWAUrl AuthenticationMethod="Fba">https://mail.myserver.com/owa/</OWAUrl>
          <Protocol>
            <Type>EXPR</Type>
            <ASUrl>https://mail.myserver.com/ews/exchange.asmx</ASUrl>
          </Protocol>
        </External>
      </Protocol>
      <Protocol>
        <Type>EXHTTP</Type>
        <Server>mail.myserver.com</Server>
        <SSL>On</SSL>
        <AuthPackage>Ntlm</AuthPackage>
        <ASUrl>https://mail.myserver.com/ews/exchange.asmx</ASUrl>
        <EwsUrl>https://mail.myserver.com/ews/exchange.asmx</EwsUrl>
        <EmwsUrl>https://mail.myserver.com/ews/exchange.asmx</EmwsUrl>
        <EcpUrl>https://mail.myserver.com/ecp/</EcpUrl>
        <EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=domain.LOCAL</EcpUrl-um>
        <EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=domain.LOCAL</EcpUrl-aggr>
        <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=domain.LOCAL</EcpUrl-mt>
        <EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=domain.LOCAL</EcpUrl-ret>
        <EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=domain.LOCAL</EcpUrl-sms>
        <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=domain.LOCAL</EcpUrl-photo>
        <EcpUrl-tm>?rfr=olk&ftr=TeamMailbox&exsvurl=1&realm=domain.LOCAL</EcpUrl-tm>
        <EcpUrl-tmCreating>?rfr=olk&ftr=TeamMailboxCreating&SPUrl=<SPUrl>&Title=<Title>&SPTMAppUrl=<SPTMAppUrl>&exsvurl=1&realm=domain.LOCAL</EcpUrl-tmCreating>
        <EcpUrl-tmEditing>?rfr=olk&ftr=TeamMailboxEditing&Id=<Id>&exsvurl=1&realm=domain.LOCAL</EcpUrl-tmEditing>
        <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=domain.LOCAL</EcpUrl-extinstall>
        <OOFUrl>https://mail.myserver.com/ews/exchange.asmx</OOFUrl>
        <UMUrl>https://mail.myserver.com/ews/UM2007Legacy.asmx</UMUrl>
        <OABUrl>https://mail.myserver.com/OAB/4b0a14e4-d177-415f-9acf-b51b966b6dd8/</OABUrl>
        <ServerExclusiveConnect>On</ServerExclusiveConnect>
      </Protocol>
      <Protocol>
        <Type>EXHTTP</Type>
        <Server>mail.myserver.com</Server>
        <SSL>On</SSL>
        <AuthPackage>Negotiate</AuthPackage>
        <ASUrl>https://mail.myserver.com/ews/exchange.asmx</ASUrl>
        <EwsUrl>https://mail.myserver.com/ews/exchange.asmx</EwsUrl>
        <EmwsUrl>https://mail.myserver.com/ews/exchange.asmx</EmwsUrl>
        <EcpUrl>https://mail.myserver.com/ecp/</EcpUrl>
        <EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=domain.LOCAL</EcpUrl-um>
        <EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=domain.LOCAL</EcpUrl-aggr>
        <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=domain.LOCAL</EcpUrl-mt>
        <EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=domain.LOCAL</EcpUrl-ret>
        <EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=domain.LOCAL</EcpUrl-sms>
        <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=domain.LOCAL</EcpUrl-photo>
        <EcpUrl-tm>?rfr=olk&ftr=TeamMailbox&exsvurl=1&realm=domain.LOCAL</EcpUrl-tm>
        <EcpUrl-tmCreating>?rfr=olk&ftr=TeamMailboxCreating&SPUrl=<SPUrl>&Title=<Title>&SPTMAppUrl=<SPTMAppUrl>&exsvurl=1&realm=domain.LOCAL</EcpUrl-tmCreating>
        <EcpUrl-tmEditing>?rfr=olk&ftr=TeamMailboxEditing&Id=<Id>&exsvurl=1&realm=domain.LOCAL</EcpUrl-tmEditing>
        <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=domain.LOCAL</EcpUrl-extinstall>
        <OOFUrl>https://mail.myserver.com/ews/exchange.asmx</OOFUrl>
        <UMUrl>https://mail.myserver.com/ews/UM2007Legacy.asmx</UMUrl>
        <OABUrl>https://mail.myserver.com/OAB/4b0a14e4-d177-415f-9acf-b51b966b6dd8/</OABUrl>
        <ServerExclusiveConnect>On</ServerExclusiveConnect>
      </Protocol>
    </Account>
</Response>
</Autodiscover>

Outlook Anywhere Prompts for Credentials only for Outlook 2010, not Outlook 2013

I'm having a heck of a time with this one. We have Exchange 2010 on premise, with our filtering through EOP. Clients that are using Outlook 2010 Professional Plus are continuously getting prompted for credentials when off network and relying
on Outlook Anywhere.
I've read many threads about configuring credential manager appropriately for the internal domain and our external domain. I can get them to authenticate just fine, and email flows, but they continue to be prompted everytime they connect again.
Here is the kicker: When I install Outlook 2013 on the same computer, outlook anywhere functions just fine, no problems, no authentication prompt.
Like I said I have read a plethera of articles and threads about this, I have gone through all settings on Exchange, our edge server, our firewall, our certificate. The MSSTD string matches our "Issued To" string. NTLM authentication
is configured on both the client and the server. Appropriate settings are configured on the firewalls.
Anyone know why Outlook 2010 would have this problem, but not Outlook 2013 on the same computer, same user, same mailbox database?
Thanks in advance!!!

I'd still Echo Ed's original question.
Do you have Outlook 2010 patched up? At this time you need to be on SP1, and SP2 by October the 14th.
Also I expect you to have a recent update ontop of that as well.
http://blogs.technet.com/b/rmilne/archive/2014/04/14/office-2010-sp2_1320_-do-you-need-to-upgrade_3f00_.aspx
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Outlook 2013 Continually Prompting For Credentials

After migrating to Office 365 & installing Pro Plus 2013, Outlook 2013 (32-bit) continues to prompt for credentials even though it shows the mailbox as connected to Exchange.
To stop this prompt, I've done the following:
Removed Outlook credentials from credential manager
Removed/recreated Outlook profiles & renamed "outlook" folder found at C:\User\"username"\AppData\Local\Microsoft\ to "Outlook.old" so Outlook will recreate the folder upon restart.
Checked Security tab of "more settings" of the mailbox to make sure "Always prompt for logon credentials" isn't checked.
Please someone give me guidance as to what else the issue could be.

Hello,
How did you set the Logon network security under More Settings on the Microsoft Exchange
Security tab? Please make sure it's not set to a value other than
Anonymous Authentication.
To verify this, please follow these steps:
1. Launch Control Panel.
2. In Control Panel, locate and click
Mail.
3. Click Show Profiles, select your Outlook profile, and click
Properties.
4. Click E-mail Accounts, select
Account Settings and on the E-mail tab, click Change.
5. In the Change Account dialog, click
More Settings.
6. In the Microsoft Exchange dialog, select the
Security tab.
7. From the Login network security
dropdown, select Anonymous Authentication and click
OK.
8. Click Next and click
Finish, and then click Close on the Account Settings dialog.
9. Click Close on the
Mail Setup dialog, and click OK to close the Mail control panel.
Please let me know the result.
Reagrds,
Steve Fan
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Windows XP Machines Always Prompt for Credentials (Exchange 2013, Outlook 2010)

I am running Exchange 2013 on Server 2012 Datacenter (VM). Windows 7 clients with Outlook 2010 work fine. Windows XP clients with Outlook 2010 prompt for credentials (user name and password) each time Outlook is started, and checking the "Remember
my password" box does not prevent this from happening the next time. The "Always prompt for logon credentials" checkbox on the "Security" tab of the "More Settings" section of the Exchange account is not checked. I have found a myriad of posts
with similar issues, but they all seem to have to do with SBS/Exchange 2007, and I haven't come across something that works as a solution for me. One suggested certificate issues, and I was having certificate security warnings, but I got that resolved.
I am hopefuly that the fact that this only happens on Windows XP will be telling.

Proxy settings:
auth_param ntlm program /usr/bin/ntlm_auth --helper-protocol=squid-2.5-ntlmssp
auth_param ntlm children 50
auth_param ntlm keep_alive on
auth_param basic program /usr/lib/squid3/squid_ldap_auth -R \
-b "DC=domain,DC=local" \
-D "CN=Squid Proxy,OU=TI,OU=Domain,DC=domain,DC=local" \
-W passldap \
-f "sAMAccountName=%s" \
-h domain.local
auth_param basic children 20
auth_param basic realm Domain Internet Proxy
auth_param basic credentialsttl 8 hours
external_acl_type ADS children=50 ipv4 ttl=60 %LOGIN /usr/lib/squid3/squid_ldap_group -S -K -b "DC=domain,DC=local" -f "(&(objectclass=person)(sAMAccountName=%v)(memberof =CN=%a,OU=Domain,DC=domain,DC=local))" -D "CN=Squid Proxy,OU=TI,OU=Domain,DC=domain,DC=local" -s sub -W ldappass domain.local
tks.

Kerberos authentication prompting for credentials in Sharepoint 2013

Hello all,
I think I’m a bit confused on what I should expect out of Kerberos and sharepoint.
Following the steps located in
http://blog.blksthl.com/2012/09/26/the-first-kerberos-guide-for-sharepoint-2013-technicians/ , I’ve setup Kerberos in my Sharepoint 2013 environment. My hope was that configuring kerberos authentication would solve the issue of users being prompted for
credentials when they access sharepoint. I know that one way to address this problem is to tweak the IE settings by adding the site to the local intranet or trusted zones, but am I wrong in thinking that Kerberos should also authenticate the user on to the
site? Here’s my situation:
Previously, I had our sharepoint URL in the trusted zone and had IE set to pass my credentials through, and that worked. After configuring Kerberos, I can see the tickets on my system using klist and the security log on our web front-end shows that I authenticated
using Kerberos.
However, if I then remove the sharepoint URL from the trusted zone in IE, I still get prompted for credentials. If I cancel the credential prompt, I get a 401 error and the security log on the server shows a NTLM login attempt.
As soon as I put the URL back in the trusted zone, I can access the site and the server log shows a Kerberos authentication.
I’m I wrong in thinking that if Kerberos was working properly then I shouldn't need to have the URL in the trusted zone?
Thanks
Bill

Thanks for the quick reply, Alex. At least it’s good to know it appears to be working as designed.
Thanks again,
Bill

Using LocationServer.xml breaks share credentials

I have multiple deployment shares setup (Production, Development, International, etc.) and I am trying to use one boot environment for all. I have followed to the documentation about LocationServer.xml, removing the DeployRoot property from Bootstrap.ini,
placed the custom LocationServer.xml in \\Share$\Extra Files\Deploy\Control, added Extra Files to the PE settings, and updated the Deployment Share to create a new iso and wim. When the deployment wizard launches it correctly
displays the location wizard with the deployment shares' friendly names in the drop down list. But when I try to connect any share it prompts for credentials, which are defined in the Bootstrap.ini. I cannot find any documentation for how to define the deployment
share user credentials within the LocationServer.xml file to automate this portion. If I cannot automate the user credentials, then the LocationServer.xml function is pretty much useless for me.
Any thoughts or suggestions?
Thanks,
Wayne C.

As a workaround you can comment out the following lines in DeployWiz_Validation.vbs
' Get the credentials and connect to the share!
oEnvironment.Item("UserID") = ""
oEnvironment.Item("UserDomain") = ""
oEnvironment.Item("UserPassword") = ""
I only comment out the userid and userdomain; this way i only need to type a password and click ok.
If you want it to be fully automated.... it looks a little tricky. Once I get my environment up 100% I may look into this further. Hopefully mdt 2012 will fix this; haven't had a chance to mess with the beta yet.

Getting Prompt for Credentials When Opening InfoPath 2010 Form in Sharepoint 2010

I have a domain user who runs Office 2010 x32 and uses a Sharepoint 2010 site daily. Lately a specific page on that site has been randomly giving prompts for credentials when opening existing documents and creating new ones. The process can be most easily
replicated by opening the new document template in Infopath by going to Documents -> New in the ribbon bar of the SP page. Most of the time the Windows credentials for the user are passed to Infopath/Sharepoint automatically (which is normal), but on the
fourth or fifth attempt to create a new form, the prompt appears. The user can still enter the credentials and open the blank template form, but a prompt should not appear. The user is also the administrator for that page, so I'm thinking it's not a permissions
issue.
The user is running IE 9 on Windows 7 Pro x64. I have performed the following:
Reset advanced IE settings and all user cache data
Cleared cached Sharepoint credentials in Windows credential manager
Re-applied group policy for the machine using gpupdate /force
Logged in with a clean temporary profile
Logged in to another domain account using the user's Sharepoint credentials
Cleared Infopath cache
Re-installed Office 2010 x32
The problem only occurs only on this particular machine. There are no Sharepoint or authentication-related errors or warnings in the application and system event logs. There are also no error messages on-screen when the prompt appears. I also considered
the possibility of this being a performance related issue in the case that maybe Infopath was taking too long to start, causing the credential pass-through process to time out and fall back to a prompt. I ran disk cleanup, deleted some temporary files, and
checked for excessive CPU/memory load. I didn't find any issues and doing these things did not help.
I'm convinced there is another setting somewhere in Windows that is causing this. Interestingly it always happens after four or five attempts, never the first time. Can someone point me in the right direction?

Hi Titan, this sounds like an IE security setting issue. Things to do:
1. In Internet options>Security>Local Intranet, make sure "Enable Protected Mode" is not selected.
2. Under Sites>Advanced, add https://*.sharepoint.com (and make sure "Require server verification..." is not checked).
3. Under Security>Custom Level, scroll all the way to the bottom and make sure "Automatic logon with current user..." is checked.
cameron rautmann

SQLServer Reporting Services 2005 Prompts for Credentials for a trusted domain user

Currently the report is running in the domain AAA. Users in the domain AAA are using the report.
Another new domain BBB and an user XXX is now created and BBB\XXX has been given Browser access. Domain AAA and BBB are trusted domains.
After this when the user BBB\XXX logs in and access the report, before loading the report, credentials dialog is prompted, once credentials of BBB\XXX is entered, the report is loaded.
Why the report prompts for this additional credential dialog for the trusted domain user?

Hello,
Did you have get two textboxes in the report parameter panel (in the left side of the "View Report" button)? The issue is occurred when the credential of the datasource is configured with “Prompt for credentials”. Please check if you configured the credential
with "Stored Credential" of the datasource.
Please refer to the following thread to configure the credential.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/1564cd7a-6b7a-40f1-9f98-5c766ebfc63e/datasource-userid-and-password-being-asked-eachtime-when-report-is-generated?forum=sqlreportingservices
Regards,
Alisa Tang
Alisa Tang
TechNet Community Support

ABAP consuming Web Service in HTTPS keeps prompting for credentials

I have a Share Point Web Service that I want
to call in HTTPS from ABAP
in an ECC 6.0 SAP_BASIS 700 SP 30 system. The
following steps have been
executed:
BASIS work completed –
SAPCRYPTOLIB, HTTPS Activation, profile
parameters, STRUST certificates
I have created the Client Proxy in SE80 for the SharePoint WCF Web Service
The Logical Port was created in SOAMANAGER
The issue I have is when I test the process using SE80 sometimes it will prompt
for credentials, sometimes it won't. The behavior is very sporadic, I
can run it once and it prompts then the second time it doesn't. This is
especially true after a restart of the system. The user and password
are on the RFC destination under consumer security tab.
Any suggestions why the prompting for
credentials?
Regards
Diane Szmurlo

Hi Sekhar,
Please see below link. It will be helpful.
Regards,
Sudha

Office Web App Prompting For Credentials Externally Only

We deployed an office web app server and it works great internally, but whenever we try to access documents externally, we are prompted for credentials. Even if we put our credentials in, we always get a 401 forbidden error. Also note that
we can access the hosting/discovery page fine internally, but not externally. Any help is appreciated.

Hi,
According to your description, I think this issue is more related to SharePoint, I suggest that you could post it to
SharePoint forum.
Regards
Starain
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

MDT 2013 and locationserver.xml prompting for credentials

Similar Messages

Maybe you are looking for