Cross-forest user administration

I have created a cross-forest trust between DSfW domain and MSAD domain. In both domains, I have added one user (call him CrossAdmin) as member of Builtin\Administrators group.
I can log in to DSfW domain as CrossAdmin and successfully administer users in MSAD domain using "Active Directory Users and Computers"). But the reverse doesn't work. If I log in to MSAD domain as CrossAdmin and in "Active Directory Users and Computers" try to switch to the DSfW domain, I get an error message:
"The domain dsfwdomain.oursite could not be found because: Access is denied".
At the same time, the following is logged to /var/log/messages on the DSfW server:
krb5kdc: [KDC] Regenerating authorization data for cross-realm client [email protected]
krb5kdc: [KDC] Failed to locate PAC principal data buffer
krb5kdc: [KDC] PAC lacks principal name authenticator
krb5kdc: [KDC] Ticket for client [email protected] is not bound to PAC
Is this a restriction by design, or can it be made to work somehow?

vatson,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://www.novell.com/support and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Forums Team
http://forums.novell.com

Similar Messages

  • Calendar permission for cross-forest users

    How can I grant mailbox folder like doctor's Outlook 2010 calendar to a cross-forest user like a receptionist. 
    The reception accepts and manages all booking for about 10 doctors and they used to work perfectly.  When reception complained that she started seeing Busy status for say 3 out of 10 doctors, I noticed the other 7 working calendars have DomainB\Reception
    explicitly added on the Calendar permission while the 3 faulty ones don't.
    When I tried:
    Add-mailboxfolderpermission -Id 'DomainADoctor1:\calendar' -user 'DomainB\Reception' -accessrights editor
    I simply get the error "The user "DomainB\Reception" is either not valid SMTP address, or there is no matching information."
    Obviously, the cross-forest permission still works but I cannot make the powershell command to work.  I have also tried the ExFolder utility to no avail.  The old Exch admin has left the company.  We use Exchange 2010 SP2
    Thank you for any assistance.

    Just to add more info, the reception mailbox is hosted on DomainA and it is linked to an external account DomainB\Reception. 
    Alternatively, I tried:
    Add-mailboxfolderpermission -Id 'DomainADoctor1:\calendar' -user 'Reception @ DomainA.com' -accessrights editor
    and the command works fine but when the Reception checks the calendar on both Outlook and OWA, she only sees "Busy" on each existing appointments and cannot add new. 
    For those calendars that work, the Editor permission shows "NT User: DomainB" while those that won't shows DomainB mailbox.
    Appreciate any help on this.

  • Cross Forest User GPOs not applying

    I know I've read a ton of forums concerning this issue and most were resolved but nothing read so far has helped and I'm really hoping there are a few ideas out there that I have missed.
    We have two forests: a new 2012 forest and an 2008 at an 2003 forest level with two way forest trust.
    We are able to login to computers in the 2012 forest regardless of domain with any user in the 2008 forest.  However we are setting up our workstation environment in the 2012 forest which requires us applying user policies.  All users are in the
    2008 forest.  We have enabled the allow cross forest policy and the loopback processing applied to the OU where the client machines are located in Active Directory.  We have verified the trust on both sides and tested DNS using nslookup on both sides.
     The DCs for both forest are located in the same physical building but two different subnets.  The WAN guy has assured us that there are no ACLs involved.  The firewall has been shut off on all DCs and all workstations.  I see no LSA errors
    on the DCs.  Each forest has a stub DNS zone to the other forest zones.  I've been able to successfully setup computer gpos to map drives to the users when they login to 2012 clients.
    I'm completely lost for what else we need to be looking at to solve this problem.   Any suggestion would be most welcome.  

    Hi,
    Before going further, what settings have we configured? Which Loopback mode have we chosen, Merger or Replace? What are operating systems of our clients?
    For further troubleshooting, we can follow the following article to collect Gpsvc.log file.
    How to enable GPO logging on windows 7 /2008 r2 ?
    http://blogs.technet.com/b/csstwplatform/archive/2010/11/09/how-to-enable-gpo-logging-on-windows-7-2008-r2.aspx
    After getting the log, you may upload it to OneDrive and provide us the download link.
    Besides, we can try using netmon.exe to further trace network to see if this is caused by network traffic.
    Microsoft Network Monitor 3.4
    http://www.microsoft.com/en-in/download/details.aspx?id=4865
    How to use Network Monitor to capture network traffic
    http://support.microsoft.com/kb/812953/en-us
    TechNet Subscriber Support
    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.
    Best regards,
    Frank Shen

  • Local forest roaming profiles with remote forest users within RDS?

    We have been using RDS for some time now. New users get a new profile from (*1)"\\domain_1\netlogon\Default User.v2" when they first logon to a RDS session host. Ones that is done, the profile is becomes roaming profile that is stored on (*2) "\\some_serverx_in_domain_1\profiles$\%username%".
    (Note, this last setting can be set in 4 different places. We used a GPO and used the Remote Desktop Services section to set it) 
    So far, no rocket science. Now...
    Recently we've been asked to allow user accounts from another (trusted) forest (domain_2) to our RDS environment. These users are able to logon to our RDS environment but they do not get a fresh profile from our (*1) default profile location. Instead, they
    get a default profile from the RDS session host and this new profile does not become roaming so it is not saved to our (*2) location. How can we force the foreign accounts to get a roaming profile within domain_1 without having to change anything outside our
    administrative border?  
    Note: Their logon servers do not have a "Default User.v2" in their netlogon and their roaming profile settings are set in the AD properties for the user accounts. The roaming profiles they use are pre-2008 and thus unusable for our 2008-R2 RDS environment.
    We are not looking for cross-forest roaming profile functionality. We just want foreign accounts to use our roaming profile setup. Please Help! 

    Hi,
    Thanks for your post.
    Make sure the trusted forest user have permission to access the Default User profile. In addition, ensure the following policy was enabled:
    Computer Configuration\Administrative Templates\System\Group Policy\Allow Cross-Forest User Policy and Roaming User Profiles
    Allows User based policy processing, Roaming User Profiles and User Object logon scripts for cross forest interactive logons. This setting affects all user accounts interactively logging on to a computer in a different forest when a Cross Forest or 2-Way
    Forest trust exists.
    How to troubleshoot Group Policy object processing failures that occur across multiple forests
    http://support.microsoft.com/kb/910206
    Best Regards,
    Aiden
    TechNet Subscriber Support
    If you are
    TechNet Subscription
    user and have any feedback on our support quality, please send your feedback
    here.
    Aiden Cao
    TechNet Community Support

  • Exchange 2013 Untrusted Cross-Forest Availability Intermittently Working

    Goal:
    I’m attempting to configure cross-forest availability for Exchange 2013 using the instructions here:
    http://technet.microsoft.com/en-us/library/bb125182%28v=exchg.150%29.aspx
    At the very bottom of the page are three different methods.  I have tried the first (per-user) and the third (untrusted) methods, with identical results.  For various unfortunate reasons, I am unable to use the Microsoft Federated Gateway for availability
    information (although that is configured in the production domain and I would use it if it were possible). 
    Situation:
    When attempting to view availability information in either OWA or Outlook, the free/busy information typically isn’t visible.  If you open and close Outlook a few times, creating meetings with the users in other domains, sometimes the other user’s information
    will be visible, and sometimes it will not.  When it is not, the area is filled with diagonal lines and hovering over it says “No Information”.  The situation is the same in both Adatum trying to access Contoso, and in Contoso trying to access either
    Adatum or Fabrikam.
    I’m currently close to finishing up my third week with Microsoft Support on this issue, and am starting over with a third first level support person.  They are quickly eroding what little confidence I had in them already.  I’m posting here because
    I’m desperate, and web searches for my errors turn up zero results.  I fear this method of availability sharing doesn’t actually work correctly in Exchange 2013 as Microsoft is pushing organizations to use the Microsoft Federated Gateway, but I’d love
    to heave about anyone getting this to work, or not.
    Setup:
    There are three separate domains I am working with (names changed to protect the innocent).  Contoso.local is the production domain, containing Exchange 2007 and Exchange 2013 SP1 servers.  Adatum.local is a test domain set up fresh with Exchange
    2013 SP1.  Fabrikam.com is a remote Exchange system that I others are connecting to without issue using Exchange 2010.
    The Contoso and Adatum domain controllers are running Windows Server 2008 R2 SP1 and are running at a 2008 R2 functional levels.  The Exchange 2013 servers are all at SP1 (results were the same prior to SP1), and the OS is Windows Server 2012. 
    Contoso has two sites, connected via 10Gbps links, and ~10ms latency, with Exchange 2013 CAS and mailbox servers in both sites.  Adatum has a single site, and has two CAS and two mailbox servers.  Fabrikam has one internet facing server to connect
    to.  A handful of contacts have been created in both Contoso and Adatum for the other domains, to select to view availability.
    Contoso and Adatum domains sit on different subnets, but there is no firewall or filtering between their subnets.  Routing between them is completely unimpeded.  The Fabrikam server sits on another network across the internet, but firewalls have
    been configured and I can browse the availability website from the Contoso CAS servers.
    The CAS servers were originally set up to be load balanced, but working with Microsoft they’ve had me specify a single CAS server for autodiscover/EWS/ECP/OWA/etc in both Contoso and Adatum.  The number of actual users on Exchange 2013 in Contoso is
    ~10.  In Adatum, there are only a handful of mailboxes configured.  The Exchange 2007 servers in Contoso are using Public Folders for free/busy replication for other domains right now, and we don’t care at the moment if they can use the 2013 availability. 
    None of our testing/configurations have involved the Exchange 2007 servers.  There are no SPNs configured for the other domains in AD.
    Errors:
    There are three basic errors that are returned in Outlook diagnostics.  The first is the timeout error.  For a given mailbox server, the first time it is queried for availability information for a remote domain (after some amount of time of being
    idle) it might not respond for 70 seconds (actually somewhere between 69 and 70 seconds each time when viewing the IIS logs), and eventually fails with the timeout error.  If it doesn’t timeout, then it will respond with the Correct Response.
    Once a particular mailbox server has timed out, it will typically immediately return the first Availability Error for all subsequent calls.  Less frequently, it will return Availability Error 2.  If a mailbox server returns the first Availability
    Error, then it will continue to return that error until it times out again or starts working.  Similarly, if a mailbox server returns the second Availability Error, then it will continue to return that error until it times out again or starts working.
    If an IISRESET is performed on a mailbox server, then it will either timeout at the next cross-forest availability request, or work.  There is never an issue accessing availability information for users in the same domain as the request.
    If the remote Exchange is in an errored state, then the response includes the error.  For example, if the mailbox servers in the remote domain are turned off, and the local mailbox server that you are querying happens to be responding correctly
    for the remote domain, then it will return an error about how no mailbox servers are available in adatum.local to service the request.
    There are no Event Log errors that correspond to failed requests of any type.  IIS logs don’t show anything beyond what is shown in the Outlook diagnostics.  There are no DNS or Active Directory Replication errors in the Event Logs.
    Timeout error:
    CalendarEvents       : {}
    ViewType             : None
    MergedFreeBusyStatus : {}
    WorkingHours         :
    Result               : Error
    ErrorCode            : ErrorTimeoutExpired
    ErrorMessage         : Microsoft.Exchange.InfoWorker.Common.Availability.TimeoutExpiredException: Request could not be processed in time. Timeout occurred during 'LookupRecipientsBatchBegin'.
                           . Name of the server where exception originated: Mailbox01
    ErrorDetails         : {}
    ErrorProperties      : {}
    Availability Error:
    CalendarEvents       : {}
    ViewType             : None
    MergedFreeBusyStatus : {}
    WorkingHours         :
    Result               : Error
    ErrorCode            : ErrorProxyRequestProcessingFailed
    ErrorMessage         : Unable to send cross-forest request for mailbox <Free BusyTest>SMTP:[email protected] because of invalid configuration., inner exception: Microsoft.Exchange.InfoWorker.Common.Availability.AutoDiscoverFailedException:
    AvailabilityAddressSpace 'adatum.local' couldn't be used because the Autodiscover endpoint couldn't be discovered.
                           . Name of the server where exception originated: Mailbox01
    ErrorDetails         : {}
    ErrorProperties      : {}
    Availability Error 2:
    CalendarEvents       : {}
    ViewType             : None
    MergedFreeBusyStatus : {}
    WorkingHours         :
    Result               : Error
    ErrorCode            : ErrorProxyRequestProcessingFailed
    ErrorMessage         : Unable to send cross-forest request for mailbox <Free BusyTest>SMTP:[email protected] because of invalid configuration., inner exception: Microsoft.Exchange.InfoWorker.Common.Availability.AddressSpaceNotFoundException:
    Configuration information for forest/domain swelab.wayad.corp.wayport.net could not be found in Active Directory.
                              at Microsoft.Exchange.InfoWorker.Common.Availability.TargetForestConfigurationCache.FindByDomain(OrganizationId
    organizationId, String domainName)
                              at Microsoft.Exchange.InfoWorker.Common.Availability.QueryGenerator.GetTargetForestConfiguration(EmailAddress
    emailAddress)
                           . Name of the server where exception originated: Mailbox02
    ErrorDetails         : {}
    ErrorProperties      : {}
    Working:
    CalendarEvents       : {Microsoft.Exchange.WebServices.Data.CalendarEvent}
    ViewType             : FreeBusyMerged
    MergedFreeBusyStatus : {Free, Free, Free, Free...}
    WorkingHours         : Microsoft.Exchange.WebServices.Data.WorkingHours
    Result               : Success
    ErrorCode            : NoError
    ErrorMessage         :
    ErrorDetails         : {}
    ErrorProperties      : {}
    Start : 04/09/2014 00:00:00
    End : 04/12/2014 00:00:00
    Subject :
    Location :
    Testing Methodologies:
    While it is possible to dig through Outlook diagnostics and OWA, we ended up scripting out these requests to save time.  Microsoft support refuses to use the scripts, but they produce the same output that it takes them days to find in the logs, so I’ll
    post them here to help anyone in the future.
    Through reading the documentation and experimenting, it appears that the Exchange 2013 CAS servers really do just proxy availability requests from the client to the mailbox servers.  At least by default, it seems to pick a mailbox server in the same
    site, but which mailbox server in the site appears to be random.  It will typically pick the same one repeatedly for a while.
    The first script uses the Microsoft Exchange Web Services Managed API 2.1.
    http://www.microsoft.com/en-us/download/details.aspx?id=42022
    You specify a source email address, and a target address in the remote domain, and it creates a SOAP request that it sends to a CAS server of the source email address.  The CAS proxies the request to the mailbox server which either responds with a failure
    or the free/busy data.
    The second script takes the XML SOAP request generated by the first script, and uses that to query a mailbox server directly.  That allows you to test specific mailbox servers that are working or failing, instead of randomly using whichever mailbox
    server the CAS happens to select.  I generated a SOAP request with the first script that I knew had some data, and then copy/pasted it into the second script to verify if data was being returned.
    I’ve deleted and recreated the availability address spaces in Contoso and Adatum for each other and Fabrikam multiple times.  I’ve reset the password in the OrgWideAccount in both Adatum and Contoso, and viewed the lastBadPassword attribute in both
    ADs to verify it wasn’t failing authentication.  (A failed authentication also generates a 401 error that is returned to the client.)  I can access the availability site of the other domain using the credentials of the OrgWideAccount without any
    errors ever.
    First Script:
    # Import the Exchange Web Services module
    Import-Module -Name "C:\Program Files (x86)\Microsoft\Exchange\Web Services\2.1\Microsoft.Exchange.WebServices.dll"
    # Create the services object used to connect to Exchange
    # You can specify a specific Exchange version, which I had to do to connect to 2007
    # Exchange2007_SP1
    # Exchange2010
    # Exchange2010_SP1
    # Exchange2010_SP2
    # Exchange2013
    # $ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2007_SP1
    # $Service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)
    $Service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService
    $Service.UseDefaultCredentials = $true
    # Specify an SMTP address. The autodiscover URL from the associated mailbox will be used to connect to Exchange
    # This is used to distinguish resolving from the 2007 server versus 2013
    #$Service.AutodiscoverUrl("[email protected]") # For Exchange 2007
    $Service.AutodiscoverUrl("[email protected]") # For Exchange 2013
    # Increase the amount output at the end to include the SOAP commands
    $Service.TraceEnabled = $true
    # Specify time frame to get free/busy for
    $StartTime = [DateTime]::Parse([DateTime]::Now.ToString("yyyy-MM-dd 0:00"))
    $EndTime = $StartTime.AddDays(7)
    # Create the various objects needed to perform the EWS request
    $drDuration = new-object Microsoft.Exchange.WebServices.Data.TimeWindow($StartTime,$EndTime)
    $AvailabilityOptions = new-object Microsoft.Exchange.WebServices.Data.AvailabilityOptions
    $AvailabilityOptions.RequestedFreeBusyView = [Microsoft.Exchange.WebServices.Data.FreeBusyViewType]::DetailedMerged
    $Attendeesbatch = New-Object "System.Collections.Generic.List[Microsoft.Exchange.WebServices.Data.AttendeeInfo]"
    $attendee = New-Object Microsoft.Exchange.WebServices.Data.AttendeeInfo($userSMTPAddress)
    # Specify SMTP addresses of accounts to request availability for
    #$Attendeesbatch.Add("[email protected]")
    $Attendeesbatch.Add("[email protected]")
    #$Attendeesbatch.Add("[email protected]")
    #$Attendeesbatch.Add("[email protected]")
    # Clear out old results so that a failed request doesn't show information still
    $availresponse = ""
    # Request the availability information from Exchange
    $availresponse = $service.GetUserAvailability($Attendeesbatch,$drDuration,[Microsoft.Exchange.WebServices.Data.AvailabilityData]::FreeBusy,$AvailabilityOptions)
    # Show summary information that would include errors
    $availresponse.AttendeesAvailability
    # Show all of the appointments in the requested time period
    foreach($avail in $availresponse.AttendeesAvailability){
    foreach($cvtEnt in $avail.CalendarEvents){
    "Start : " + $cvtEnt.StartTime
    "End : " + $cvtEnt.EndTime
    "Subject : " + $cvtEnt.Details.Subject
    "Location : " + $cvtEnt.Details.Location
    Second Script:
    # Change the server in this URL to specify which mailbox server to access
    $url = 'https://mailbox01.contoso.local:444/EWS/Exchange.asmx'
    # Uncomment the below lines if you want to query EWS using credentials other than
    # the ones used to run the script.
    #If(!(Test-Path variable:global:cred))
    # $cred = Get-Credential
    function Execute-SOAPRequest
    [Xml] $SOAPRequest,
    [String] $URL
    write-host "Sending SOAP Request To Server: $URL"
    $soapWebRequest = [System.Net.WebRequest]::Create($URL)
    # These appear to be the only things needed in the headers when making the request
    $soapWebRequest.ContentType = 'text/xml;charset="utf-8"'
    $soapWebRequest.Accept = "text/xml"
    $soapWebRequest.Method = "POST"
    If(Test-Path variable:global:cred)
    $soapWebRequest.Credentials = $cred
    Else
    $soapWebRequest.UseDefaultCredentials = $true
    write-host "Initiating Send."
    $requestStream = $soapWebRequest.GetRequestStream()
    $SOAPRequest.Save($requestStream)
    $requestStream.Close()
    write-host "Send Complete, Waiting For Response."
    $resp = $soapWebRequest.GetResponse()
    $responseStream = $resp.GetResponseStream()
    $soapReader = [System.IO.StreamReader]($responseStream)
    $ReturnXml = [Xml] $soapReader.ReadToEnd()
    $responseStream.Close()
    write-host "Response Received."
    return $ReturnXml
    # The specing and line returns in the below variable are important for some reason
    # For example, there must be a line return after the @' on the first line, or it's invalid...
    # Change the line with this:
    # <t:Address>[email protected]</t:Address>
    # to the email address in the domain you want to query
    $soap = [xml]@'
    <?xml version="1.0" encoding="utf-8"?>
    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Header>
    <t:RequestServerVersion Version="Exchange2013_SP1" />
    <t:TimeZoneContext>
    <t:TimeZoneDefinition Name="(UTC-06:00) Central Time (US &amp; Canada)" Id="Central Standard Time">
    <t:Periods>
    <t:Period Bias="P0DT6H0M0.0S" Name="Standard" Id="Std" />
    <t:Period Bias="P0DT5H0M0.0S" Name="Daylight" Id="Dlt/1" />
    <t:Period Bias="P0DT5H0M0.0S" Name="Daylight" Id="Dlt/2007" />
    </t:Periods>
    <t:TransitionsGroups>
    <t:TransitionsGroup Id="0">
    <t:RecurringDayTransition>
    <t:To Kind="Period">Dlt/1</t:To>
    <t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
    <t:Month>4</t:Month>
    <t:DayOfWeek>Sunday</t:DayOfWeek>
    <t:Occurrence>1</t:Occurrence>
    </t:RecurringDayTransition>
    <t:RecurringDayTransition>
    <t:To Kind="Period">Std</t:To>
    <t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
    <t:Month>10</t:Month>
    <t:DayOfWeek>Sunday</t:DayOfWeek>
    <t:Occurrence>-1</t:Occurrence>
    </t:RecurringDayTransition>
    </t:TransitionsGroup>
    <t:TransitionsGroup Id="1">
    <t:RecurringDayTransition>
    <t:To Kind="Period">Dlt/2007</t:To>
    <t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
    <t:Month>3</t:Month>
    <t:DayOfWeek>Sunday</t:DayOfWeek>
    <t:Occurrence>2</t:Occurrence>
    </t:RecurringDayTransition>
    <t:RecurringDayTransition>
    <t:To Kind="Period">Std</t:To>
    <t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
    <t:Month>11</t:Month>
    <t:DayOfWeek>Sunday</t:DayOfWeek>
    <t:Occurrence>1</t:Occurrence>
    </t:RecurringDayTransition>
    </t:TransitionsGroup>
    </t:TransitionsGroups>
    <t:Transitions>
    <t:Transition>
    <t:To Kind="Group">0</t:To>
    </t:Transition>
    <t:AbsoluteDateTransition>
    <t:To Kind="Group">1</t:To>
    <t:DateTime>2007-01-01T06:00:00.000Z</t:DateTime>
    </t:AbsoluteDateTransition>
    </t:Transitions>
    </t:TimeZoneDefinition>
    </t:TimeZoneContext>
    </soap:Header>
    <soap:Body>
    <m:GetUserAvailabilityRequest>
    <m:MailboxDataArray>
    <t:MailboxData>
    <t:Email>
    <t:Address>[email protected]</t:Address>
    </t:Email>
    <t:AttendeeType>Required</t:AttendeeType>
    <t:ExcludeConflicts>false</t:ExcludeConflicts>
    </t:MailboxData>
    </m:MailboxDataArray>
    <t:FreeBusyViewOptions>
    <t:TimeWindow>
    <t:StartTime>2014-04-03T00:00:00</t:StartTime>
    <t:EndTime>2014-04-10T00:00:00</t:EndTime>
    </t:TimeWindow>
    <t:MergedFreeBusyIntervalInMinutes>30</t:MergedFreeBusyIntervalInMinutes>
    <t:RequestedView>DetailedMerged</t:RequestedView>
    </t:FreeBusyViewOptions>
    </m:GetUserAvailabilityRequest>
    </soap:Body>
    </soap:Envelope>
    $ret = Execute-SOAPRequest $soap $url
    # Uncomment out one of the below two lines to get output in different alternative formats
    #$ret | Export-Clixml c:\temp\1.xml;Get-Content c:\temp\1.xml
    #$ret.InnerXml
    # If the request is successful, show the appointments, otherwise show the failure message
    If ($ret.Envelope.Body.GetUserAvailabilityResponse.FreeBusyResponseArray.FreeBusyResponse.ResponseMessage.ResponseClass -eq 'Success')
    $ret.Envelope.Body.GetUserAvailabilityResponse.FreeBusyResponseArray.FreeBusyResponse.FreeBusyView.CalendarEventArray.CalendarEvent
    Else
    $ret.Envelope.Body.GetUserAvailabilityResponse.FreeBusyResponseArray.FreeBusyResponse.ResponseMessage

    In this case, the SMTP domain is the same as the AD domain.  If the wrong domain were configured then the connection would never work, as opposed to sometimes work.
    RunspaceId            : abb30c12-c578-4770-987f-41fe6206a463
    ForestName            : adatum.local
    UserName              : adatum\availtest
    UseServiceAccount     : False
    AccessMethod          : OrgWideFB
    ProxyUrl              :
    TargetAutodiscoverEpr :
    ParentPathId          : CN=Availability Configuration
    AdminDisplayName      :
    ExchangeVersion       : 0.1 (8.0.535.0)
    Name                  : adatum.local
    DistinguishedName     : CN=adatum.local,CN=Availability Configuration,CN=Wayport,CN=Microsoft
                            Exchange,CN=Services,CN=Configuration,DC=contoso,DC=local
    Identity              : adatum.local
    Guid                  : 3e0ebc2c-0ebc-4be8-83d2-077746180d66
    ObjectCategory        : contoso.local/Configuration/Schema/ms-Exch-Availability-Address-Space
    ObjectClass           : {top, msExchAvailabilityAddressSpace}
    WhenChanged           : 4/15/2014 12:33:53 PM
    WhenCreated           : 4/15/2014 12:33:35 PM
    WhenChangedUTC        : 4/15/2014 5:33:53 PM
    WhenCreatedUTC        : 4/15/2014 5:33:35 PM
    OrganizationId        :
    OriginatingServer     : dc01.contoso.local
    IsValid               : True
    ObjectState           : Unchanged

  • Cross Forest Migration from Exchange 2007 to Exchange 2013

    Hi
    Could anybody advice me the steps also the  pros and cons for below mentioned environment if we are going for the cross forest migration.
    Source 
    Domain -   test.local
    Active Directory -  Windows 2003
    Exchange Server - 2007
    Target
    Domain -   test.net
    Active Directory -  Windows 2012
    Exchange Server - 2013
    Also if it is possible ,
    How could I remove the source environment including the exchange servers. after the migration ?
    Regards
    Muralee

    Hi Oliver ,
    Please suggest us.               
     In my environment we are in a plan to migrate from exchange 2007 to exchange 2013 (cross forest migration).
    Source : Exchange 2007 with sp3 ru 10 
    Target : Exchange 2013 with cu2 ( new environment yet to be created).
    Trust : Forest trust in place (two way )
    Domain and forest functional level : 2003 in both target and source  
    Migration Steps :
    Step1 :
    We are in a plan to execute 'preparemoverequest.ps1' first in the target forest ,so that we will get the disable MEU
    in the target forest.
    Step2:
    Then we are going to use ADMT to migrate users SID'S and password .
    Step3:
    Then we are going to move the mailboxes with New-moverequest  
    Please have a look in to our steps and suggest us ,whether we are going to proceed the migration in a right way or not
    .Is anything needs to be changed please intimate me .
    Thanks 
    S.Nithyanandham 
    Hey there,
    Sorry for taking a little while to get back to you, i've been busy working on Hosted Lync deployments!
    Use ADMT first, then when using preparemoverequest.ps1 script using the -uselocalobject cmdlet. This will then tie it up to the ADMT migrated account.
    More info in this thread here: http://social.technet.microsoft.com/Forums/windowsserver/en-US/2916e931-36a0-4ba4-8c04-196dbe792b44/preparemoverequestps1-and-admt?forum=winserverMigration
    Oliver
    Oliver Moazzezi | Exchange MVP, MCSA:M, MCITP:Exchange 2010,MCITP:Exchange 2013, BA (Hons) Anim | http://www.exchange2010.com | http://www.cobweb.com | http://twitter.com/OliverMoazzezi

  • Need help on Cross Forest Exchange 2007 - 2013 with Linked Mailboxes

    Hey all,
    So I'm in a bit of a pickle with my Exchange design and am trying to figure out if there's a way to migrate mailboxes across forests where Linked mailboxes are being used. I've done a bit of reading and have noted stuff like preparing the move request in
    AD, etc. But I'm wondering if someone can break it down for me.
    http://1drv.ms/1lWjLqG
    The above is a OneNote diagram of how we have moved over time. Please forgive my sloppy handwriting but I hope it gets the point across. I will text it out here as well:
    Original Design
    The original design of the domains when I joined the company were fabrikam and contoso. Contoso is a domain that sits entirely in the "DMZ". Fabrikam was the internal AD forest where most services and users authenticated to. In Contoso, there
    are 2 domain controllers, the "Front End" Exchange Server (Edge Transport), and the "Back End" server, which is CAS/Mailbox.
    There is a forest trust between contoso and fabrikam where "Linked Mailboxes" are created in Contoso, and then the LinkedMasterAccount is set to Fabrikam.
    Migration/Hybrid Design
    Due to the fact that these two domains were configured massively inappropriately, riddled with security holes as well as strange permissions configurations, the decision was made to create a new internal AD domain. In my OneNote, I've labeled this 'specialbank.com'.
    A long while ago we migrated users from Fabrikam to SpecialBank via trusts. To facilitate access to Exchange, a new trust was created between Contoso and SpecialBank to allow us to update the LinkedMasterAccount parameter to the new Specialbank domain.
    We have most of our users authenticating to their mailboxes via SpecialBank, while the mailboxes still reside in Contoso.
    Migration from Exchange 2007 to Exchange 2013
    I am attempting to now figure out the best way to migrate the mailboxes from Contoso to a new set of Mailbox servers in SpecialBank. This will also be an upgrade from Exchange 2007 (Current) to an Exchange 2013 installation.
    The latest Service Packs and CUs are installed in both.
    What would be the best procedure to move these mailboxes? To my knowledge, the current best practice/recommended way is to perform a user/SID migration from Contoso to SpecialBank. But I already have accounts in
    SpecialBank that users are actively using.
    I'm not opposed to doing a simple PST export from Contoso to SpecialBank, but we're looking at around 120 mailboxes. So I'm trying to make my life a little easier instead of spending a weekend here.
    If I try to do it in batches, I need to figure out how to handle autodiscover and CAS. Since I'm creating an entirely new Exchange environment, I'm trying to limit what I place in the existing configuration. But I'm not opposed to setting up something temporarily
    if I need to in order to make the migration transparent to users.
    Can anyone help?

    Hi ,
    From you description i came to know contoso is the resource forest and special bank is the account forest .
    You just wanted to migrate the linked mailboxes from resource forest to account forest and also you would want the migrated mailboxes to get merged to the respective user accounts in the account forest to become as a normal user mailbox.Am i right ?
    Please correct me if i am wrong . I have found some blogs in internet please have a look in to that especially the first one.
    http://www.outlookforums.com/threads/60210-cross-forest-mailbox-move-and-linked-mailbox/
    http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_27974905.html
    Regards
    S.Nithyanandham
    Thanks S.Nithyanandham

  • Cross-forest access to public folders Exchange 2013-2007

    Dear.
    We have an Exchange 2007 org in one forest and an Exchange 2013 org in another forest.
    User accounts remain in the 2007 AD, mailbox moved to Exchange 2013 in the other forest, so a linked mailbox.
    What do I need to do in the Exchange 2007 public folders to give the migrated mailboxes (not migrated users) access to these public folders?
    Thanks for the support.
    Regards.
    Peter Van Keymeulen, IT Infrastructure Solution Architect, www.edeconsulting.be

    Hi Stephen,<o:p></o:p>
    <o:p> </o:p>
    Do you have trust between Exchange 2007 forest and Exchange 2013 forest? Please set up a trust between the two forests. Then set the public folder client  permission
    to see if we can access the
    public folders.<o:p></o:p>
    <o:p> </o:p>
    If not, since Public folder cross forest migration is not supported in from an Exchange 2007/2010 forest to an exchange 2013 forest, refer to forum:
    http://social.technet.microsoft.com/Forums/office/en-US/51da1b97-fbb1-4f81-87da-c3370960c4ab/crossforest-public-folder-migration?forum=exchangesvrdeploy
    http://social.technet.microsoft.com/Forums/office/en-US/663f0dc3-a977-408a-93c7-94584fbefc62/public-folder-issue-cross-forest-migration-exchange-2010-to-2013?forum=exchangesvrdeploy
    <o:p></o:p>
    Title: Migrate Public Folders to Exchange 2013 From Previous Versions<o:p></o:p>
    Link:
    http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx<o:p></o:p>
    <o:p> </o:p>
    So for public folder migration,
    the only supported path is cross forest 2007/2010 to 2007/2010 and then inter forest 2007/010 to 2013. Or
    we can first export all the public folder to PST from the Exchange 2007 forest, then import the PST to the Exchange 2013 forest.
    <o:p></o:p>
    Regards, Eric Zou

  • SCCM 2012SP1 - Cross Forest Scenario

    Guys/Girls
    I've configured a cross forest SCCM scenario, with all the SCCM config in one Forest and a single Windows XP SP3 desktop in the other. There is a trust between both Forests/2-way external but I haven't added Forests/Domain to SCCM to enable searching
    etc. I deployed the agent manually in the external Forest using a mapped drive and ccmsetup /mp:........ this all works fine.
    After installation, after the client is approved, when I click on the client in the SCCM console and try to initiate any of the "right-click" features, I just get a stack of access denied errors back "0x80070005". I've tried rebuilding
    WMI, re-installing the client to no avail. Im thinking that its related to the cross forest config but I see no provision for setting up external credentials for the other forest - am I right in thinking that the only account that needs to be configured is
    the "Network Access Account" that the agent uses to make network connections (the rest being run under the guise of the "Local System" account) if so - this is already done too.
    I'm not seeing any access denied entries on the XP desktop and I've been through the DCOM config and local policy to make adjustments/slacken off the permissions...still no dice.
    Am I chasing my tail with this? can I manage a client from the console that actually sits outside of the Forest where the SCCM installation is actually installed?
    The installation is pretty much inline with scenario 1 from the following blog:
    http://blogs.technet.com/b/neilp/archive/2012/08/20/cross-forest-support-in-system-center-2012-configuration-manager-part-1.aspx
    -a

    Reading more closely, I notice now that you said "right-click tools". That explains it as those truly have nothing to do with ConfigMgr. Essentially, what all right-click tools are are individual scripts run on your local system that directly connect
    to the remote system to perform an action. The console initiates these scripts but that's it. Thus, the credentials of the user logged into the console are used to launch those scripts and the problem here is that the user you are running the console
    as does not have permissions to remotely connect to that remote system.
    As mentioned, this has nothing to do with ConfigMgr though because ConfigMgr never ever connects to remote clients -- call client agent communication is initiated by the client.
    Thus, the right-click tools, while sometimes/often useful, should not be confused with native ConfigMgr functionality.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • Kerberos Authentication Setup for MSCRM in cross forest oneway trust environment.

    Dear All,
    Kindly help related to implement Kerberos authentication on CRM application with multiple Forest environment. My environment details are as below:
    Number of forests: 2
    1. First is with name of domain1.local
    2. Second is with name of domain2.local
    Trust Level: One Way trust from domain1 and domain2.
    CRM Farm Details:
    1.  1 CRM(APP + WEB)Server (CRMAPP-01.domain1.local)
    2.  1 SQL Server (CRMSQL-01.domain1.local)
    3. 1 CRM SSRS Server (CRMSSRS-01.domain.local)
    4. CRM site url: http://mscrminternal.domain.local/MSORG1
    *I have successfuly configured Kerberos authentication and everything is working fine once try to access for Users of domain1.
    But once I tried to access for users of domain2. I am getting following error.
    HTTP Error 401 - Unathorized: Access denied.
    *If i switch to NTLM, I can access CRM site for domain2 and domain1 users without any issue.
    I read MS article, Kerberos delegation can be established if one way FOrest trust is present.
    Please help me to understand if Kerberos is possible to setup cross forest oneway trust.
    Regards
    Gyan
    GYAN SHUKLA

    Hi Gyan,
    I assume that you have solved this issue by synchronizing time between Domain Controllers, right?
    Then your last reply should be marked as answer.
    If this issue still persists, pelase feel free to let us know.
    Best Regards,
    Amy 

  • Cross forest migration Exchange 2010 SP2 to Exchange 2010 SP2

    Hi,
    We are planning cross forest migration Exchange 2010 SP2 to Exchange 2010 SP2.
    Requesting you to please help us out for below scenario.
    Source Exchange 2010 SP2:- abc.com
    2AD, 2CAS & 2 MBX servers
    Database:- 4
    Total Users :- 3500
    Accepted Domains :- 8
    Total Data:- 5TB +
    Target Exchange 2010 SP2:- xyz.com
    Resource allocated same as above.
    Now we have to migrate users along with data to target forest xyz.com keeping both setup live, as moving 5TB + data will be a ongoing process and the same will take some time.
    With the guidelines mentioned in
    http://careexchange.in/cross-forest-migration-guide-exchange-2010-to-exchange-2010/#comment-14203 we are able to migrate test users along with data, but after migration the migrated user is not able to connect through MS Outlook even not able to login into
    OWA. It gives error “The Outlook Web App address
    https://mail.abc.com/owa is out of date.”
    Kindly let us know how to solve this issue.
    Kindly let me know if you want any more information from our end.
    Thanks in advance.
    Thanks and Regards, Shashank Kudi

    Hi Shashank,
    Do you have certificates properly installed and configured in the target Exchange?
    If not, Please configure certificate and import the certificate to the trusted root CA if you are using internal CA cert.
    Thanks, MAS
    Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Gal Sync and group member sync cross forest. Not working together

      I am finalizing a cross forest migration. The End client needs an extended period of time with both domains up and running. I have been working with an advisory engineer and we are having a hard time.
      We started by setting up GAL sync and that works as expected. Then we tried to setup group provisioning, and I have that working. I can create a groups and add members, as long as those users are in FIM and the Target forest the membership information
    is preserved. During the process we removed the GAL sync agents for ease of troubleshooting. Now when I run the GAL sync agents and I search the connector space I am showing connector false on both sides. I am not sure how to correct that. The other objects
    were created by the DS agents and FIM.  If I sync a new object it will create a contact cross forest. 
      What I want it to do is run the GAL sync without group contacts. Synchronize the GAL on both sides. (Groups have been created on both sides of the domain and ADMT has moved the group membership with the user) After the GAL is synchronized I need FIM
    to synchronize the group membership adding the contacts from the missing users that have moved. I am not sure how to get that logic in the system.
      I am not sure I am going about this the right way. It may be easier to use the FIM and AD DS agents to provision users cross forest as contacts and the group membership would be preserved.  If that is the case, I am not sure how to pull
    that off.
    Does anyone have recommendations?
    Thank You

     
    This is an overview of basically how it works. 
    The Group sync is pretty much out of the box, the real key here is the User is imported to FIM and that 'Person' is then provisioned outbound as a contact. 
    Membership synchronizes with the Group and FIM maintains group membership cross forest as the source user, and the target contact are the same 'Person'. 
    Precedence is important.  The OU structure is the same on both forests and needs to be initialized.  The Groups Sync is ahead of the users and then the users sync, and the group membership
    syncs. 
    The attribute flow is a long list.  It includes all of the exchange information for the contact, and it provisions the contact as mail enabled on both sides.  There is no VB it’s all
    done in sync rules. 
    Next Ill post the attribute flow and precedence diagram, I’ll get that together this week (I hope).  I intend to put this up in a lab and get screen shots on the whole configuration. 
    I will do that as soon as I can.
    Let me know if you have questions.

  • Internal CA - Cross Forest Enrollment

    Hi,
    I'm trying to get cross-forest certificate enrollment working. My resource forest is built on Serer 2012 R2, and my accounts forest is built on Server 2008 R2.
    I have s simple setup with an offline Root CA, and an Enterprise subordinate CA.
    I have followed the steps in this article: https://technet.microsoft.com/en-us/library/ff955845(v=ws.10).aspx
    While it seems to be mostly working, I'm getting many failed requests on the Enterprise CA. Each domain controller in the accounts forest is trying to enroll a certificate every 8 hours.
    with the error:
    The permissions on the certificate template do not allow the current user to enroll for this type of certificate. 0x80094012 (-2146877422 CERTCRV_E_TEMPLATE_DENIED)
    If I right click the failure and try to issue it, the error changes to:
    Configuration informaiton could not be read from the domain controller, either because the machine is unavailable, or access has been denied. 0x80070547 (WIN32: 1351 ERROR_CANT_ACCESS_DOMAIN_INFO)
    The domain controller gets errors 13 and 6 in the event log.
    I have noticed that error 13 in the event log refers to the NT AUTHORITY\SYSTEM account (the SID is listed in the details tab).
    Is there special permissions I need to apply to get this working? Any ideas on what I need to do?
    Sorry, I do not have a great deal of experience in Certificate Services yet.
    Thankyou for your help

    In a cross forest enrollment issue, there are a few possibilities on what you have missed in your configuration.
    1) As Amy stated, did you configure permissions on the certificate template to include global/universal groups from the remote forest (and assign the group the minimum of Read and Enroll permissions)
    2) Did you enable LDAP referrals on the issuing CA so that Kerberos will allow authentication of a security principal from the remote forest.
    3) Did you replicate the certificate templates, OIDs, and Enrollment services containers fully (and successfully) from the CA forest to the remote forest.
    4) Did you validate that a two-way,  bi-directional, cross-forest trust exists between the two forests.
    Brian

  • SCOM 2012 Cross forest deployment

    Hi all,
    Is two way trust is mandatory to deploy cross forest scom 2012 if we user certificate also ?
    Thanks,
    Sengottuvel M

    Monitoring across non- trust domain
    1) two way trust between domains OR
    2) using certificate
    Roger

  • Permissions error during Cross-Forest Cert enrollment

    Hello,
    When attempting to manually enroll for a Cert on a 2012 R2 server, I get the 'Certificate types are not available' msg with the 'You cannot request a cert at this time because no certificate types are available' msg.  When I click the 'Show all templates'
    box, all the cert types are shown with a Status: Unavailable and the msg 'The permissions on the certificate template do not allow the current user to enroll for this type of cert'.
    In this instance, the CA infrastructure is in the Resource forest with the server attempting a cert enroll in the Account forest.  Both Forests are 2008 R2 with a two-way Forest Trust.  We followed all steps in the 'Cross-forest Certificate Enrollment
    with Windows Server 2008 R2' doc published by Microsoft with no issues.  The PKISync worked fine and we do see the Root and SubCA1 certs on the machine we are trying to manually enroll a cert on.  We implemented all the steps to ensure this machine
    receives a cert the same way machines in the Resource forest receive certs.  We've validated the base Trust/Network infrastructure and all checks out.  However, the Resource root forest and domain is all one and on the same domain controllers whereas
    the Account forest has the classical Forest root with two separate domain controllers and then a child domain with a number of domain controllers.  The child domain is where the server lives which we are trying to manually enroll a cert.
    As a point of clarification, the server computer account was added to a Global Security group in the Account Forest.  This group was added to a Domain Local Security group in the Resource Forest which has the Read/Enroll/AutoEnroll permissions on the
    Cert Template.
    Any suggestions on what could be causing the permissions errors?
    Thanks for your help! SdeDot

    Certificate Template permissions can never be assigned to a Domain Local group, only to Universal or Global groups.
    The correct strategy in a multi-forest scenario is the following:
    1) Create a universal group for the certificate template in the account forest (say
    Accountdomain\pki-authcert-u)
    2) Create a universal group for the certificate template in the resource forest (say Resourcedomain\pki-authcert-u)
    3) Create multiple global groups in each domain in the account forest (if three domains in the forest, create three global groups - one in each domain). Then add the user accounts to the global group in the same domain)
    4) Create multiple global groups in each domain in the resource forest (if three domains in the forest, create three global groups - one in each domain). Then add the user accounts to the global group in the same domain)
    5) On the certificate template, assign the two universal groups Read, Enroll, (and Autoenroll) permissions. That is both Accountdomain\pki-authcert-u and Resourcedomain\pki-authcert-u
    6) Run the pkisync.ps script again to replicate the new permissions
    The reason you cannot use domain local groups is that the certificate template is stored in the Configuration naming context which is replicated to each domain in the forest (account or resource in your case).
    A domain local group can only be used in the domain where the group exists (not good for PKI objects in the configuration NC.
    Brian

Maybe you are looking for

  • Function modules for Transaction SE16  for any table whole data

    Hi Experts, i need to pass report or function module input as table name:LFA1. I Need to get all the data with fileds for those table. say : i/p paramters: s_tabname  like (tabname). here s_tabname ='lfa1'. output :all the fileds details with  whole

  • Pass Passord Variable to a Batch File using Execute Process Task

    I have an FTP batch file that I want to execute using Execute Process Task. The content of the ftp (ftpscript.cmd) is as below: open ftpsite UserName Password ASCII get file  c:\temp\test.txt bye Using SSIS Execute process task, I was able to downloa

  • IWeb '08  Color of Photos on a Photo Page

    I installed iWeb '08 selected a template, choose the photo page, posted the photos but when I view them they are much darker and too red. Nothing like the original images. I can't correct them using the inspector as it does not work for photo pages.

  • Installing Oracle8i and Designer

    I am new to the installation side of Oracle and am attempting to intsall and get running Oracle8i, Designer, Forms and Reports on my NT based Laptop (Basically the package given out at iDevelop2000 (Melbourne)). So far I have Oracle8i running but can

  • 'Itunes as encountered a problem and needs to close' - (Version 6)

    Hi fellow ipoderers. As above ^ my problem is that error message on startup of itunes. Yes, i already have read posts on this before, but my problem is different because quicktime is installed PERFECTLY, and i tried to install Itunes Version 6 FROM A