ITGURU

Yes I am. external provider

I've got to the final point of an Exchange 2013 to 2016 migration. However, I have an issue with outbound email. I cannot redirect email to the new internal server IP as I don't have access to firewall, so currently I have inbound mail going to the old server which still reaches the mailboxes on the new 2016 server and sending external emails still go out via the old 2013 server. I can add a second Network connection (or add the IP as a second IP) to the new 2016 server assign it the same IP (obviously after shutting down the 2013 server) and I can then receive external mail without any issues, it all delivers fine. However, any external emails send don't go and get stuck in the queue. In the send connector I removed the 2013 server and added the 2016 one. However, if I then revert the changes, bringing the old 2013 server back online with the IP all the delayed emails then send. What have I missed and is there a way to force which interface IP the email is sent out on as I suspect that may be the issue?

I inherited a Dell R515 server which I think has an issue with the hard drives. It is fully populated with 8 x 300gb drives. Within the dell server administrator when I look at the storage controller, connector 1 it shows drives 0:0:0 through to 0:0:3 and on connector 2 drives 1:0:4 to 1:0:6. There are 2 virtual disks: Disk 1 - System - Physical Disks 0:0:0 and 0:0:1 in a Raid 1 mirrored Disk 2 - Data Drive - Physical disks 0:0:2 and 0:0:3 and 1:0:4 and 1:0:5 in RAID 10 - capacity 1.08TB after formatting. Therefore I believe that I still have 2 spare drives I can use? On the front of the server all drives have a power light, however when I go to create a virtual disk, I only get RAID 0 option. if i'm correct I should also have a 1:0:7 drive on connector 2 so I can then create a raid 1? Do I assume therefore that even though the drive has power that it could have a falty SAS connection so the server isn't seeing the drive on the data side?

Thought it might be DNS related - Found the entry still pointing to the old server. Changed it , did a ipconfig /flushdns Shut down the old server, then Outlook opened (but i did have to log off and back on first for it to take effect)

Hi, I've been carrying out an exchange 2013 to migration. All has gone well with the mailboxes and running smoothly, i've migrated all arbitration mailboxes and deleted all databases from the old 2013 server. All i believe it is doing now is receiving and sending the email for the exchange system. As a test I shut down the exchange 2013 server and then i experienced 2 issues: - Outlook showed as being disconnected whilst Outlook was open - On trying to restart it said outlook could not start so couldnt open the mailbox but OWA working fine. with the 2013 server shut down i logged on to another client and launched outlook and it just got stuck on Loading profile indefinitely I then started up the 2013 server and launched outlook and it immediately connected. Can any one help/advised on what i may have missed during the transfer so that clients still connect when the old server is decomissioned? Thanks.

Skype for business desktop client but NO on-site server, it connects to sipdir.online.lync.com:443

I am trialling Skye For Business Basic and also have an Exchange 2016 server on-site. It seems that conversations are not saving in Outlook 's Conversation History folder depsite being ticked in the options. Has anyone successfully integrated skype for business to save conversations or can help I've tried all the registry bits that come up in results online. Thanks in advance,

I see no issues with having a .local or .internal domain. I've had a .local domain since day 1 and never had any problems even with always running Exchange , syncing with Google and O365 with no problems.

Oops thanks for that! I should have realised. All working now :-) Thank you!

I am already on a newer build of Server 2016 but still cannot get the LOGIN box to load...

Hi, I have a successfully working install of Server 2012 R2 with Remote App running SIMS.net However, i have set up a new 2016 server and installed SIMS, assigned as a remote app, however I cannot get it to launch. I get a brief flash of the icon in the taskbar then it disappears, and no login box. Also the program isn't running in task manager. Can anyone help? All other apps work fine. Thanks

Hi, How do i ensure that my WSUS is fully up to date? I can get it to check in with the server itself for updates, however in products and classifications I cannot find an option for WSUS. How do i know if there are wsus patches/updates that have been released as since the clean install of Server 2016 and adding the WSUS role, i've never applies any WSUS updates, just the normal monthly cumulative updates. Thanks

I'm confused also then! I only reply to threads that come up on 'todays posts' or 'new posts'

I just use windows routing and remote access, connect to a server on-site using SSTP then have full access to all IPs on all VLANs too so from my local machine at home I can access anything as if on -site.

Our PSF has always been in the psfcloud since we moved away from sap. Available anywhere with Remote Desktop app even though we do have RemoteApp.

No need for it to be internet connect. it's on a separate VLAN and accessible via VPN both on phone and computer if access is needed off-site.

Sorted it i had to run run netsh winhttp reset proxy as i'd previously put the proxy in (without exceptions) so that exchange could check for updates at the start of the install

Hi, Things are progressing well however come across something which i have just noticed on both the test and live enrvironment. from the Exchange management shell on the new 2016 server, i get the following error message when launching the exchange shell when it tries to connect to either the 2013 or 2016 server, but still works fine from the 2013 server. VERBOSE: Connecting to server.domain.local. New-PSSession : [server.domain.local] Connecting to remote server server.domain.local failed with the following error message : The WinRM client cannot process the request because the server name cannot be resolved. For more information, see the about_Remote_Troubleshooting Help topic. At line:1 char:1 + New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Micr ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin gTransportException + FullyQualifiedErrorId : ComputerNotFound,PSSessionOpenFailed Does it work OK in your environment from the 2016 server? The exchange 2016 server is running on Windows Server 2016 Thanks

What version of exchange and what cumualtive update? Any chance you've installed the latest dot net, as I know thats only compatible with some updates. maybe uninstall the updates then reboot ?

Are you not using SSL forms authentication? What was the last update/updates you did?

Packet loss externally will be due to firewall. Jsut tried to access and see you get Http/1.1 Service Unavailable so in IE on-site if you browse to http://mail.romanhill-pri.suffolk.sch.uk/owa you get the login page?

Souns like DNS - what if you ping the URL internally and externally, does it resolve to correct destination? have you applied any windows update or exchange updates? Check the bindings in IIS have the domain name in there

Thank you, i have done this is a test environment up to the point of the Final steps mentioned and seems to be a smooth transition. Seems to be the easiest migration so far having done this since exchange 2000.

I currently have a single exchange 2013 server which provides all roles, with an internal and external DNS name of webmail.domain.com I am planning to migrate this to a new exhange 2016 server. All internal clients are Outlook 2016. A couple of questions before i start the migration: - I know that when i install the 2016 server i may get certificate warnings in Outlook, so does the new servers dns need to have a different dns name both internally and externall i.e mail.domain.com or can i change them to be the same name as the exchnage 2013 server and import the ssl certificate to the new server from the old one so that when dns changes are made the new server can be pointed at using the same name so activesync clients etc don't need to re-configure. - Do i then change the internal and external dns entries to the new 2016 server IP of which the 2016 server will proxy back to mailboxes on the 2013? - what should the externaluri and internaluri be for both the servers once the new 2016 server is installed?

Perhaps they need to think about making case sensitive passwords also for SIMS.