When our Windows 10 devices print from Microsoft Edge the print hits the Window Server 2012 print queue, and just hangs at printing/spooling. This goes on until I manually clear the queue, and restart the print-spooler. As far as I have seen, the only program with printing issues is Edge.
Is this a driver issue? Where does one start fixing this?
I have an Exchange 2016 Server which bsods with about 14 days inbetween. The server is virtual and exists in a clustered vmware environment with storage via iSCSI. None of the other Windows servers we have running (including the passive copy of Exchange) bsods. The passive Exchange is beeing backed up and clears the transaction-logs as it should on both the passive and active node.
Here is what BSoD viewer gives me of information:
052716-21921-01.dmp 27.05.2016 10:22:16 CRITICAL_PROCESS_DIED 0x000000ef ffffe000`de10d080 00000000`00000000 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+14e3a0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.3.9600.18289 (winblue_ltsb.160328-1315) x64 ntoskrnl.exe+14e3a0 C:\Windows\Minidump\052716-21921-01.dmp 8 15 9600 138 150 27.05.2016 10:22:47
051516-25765-01.dmp 15.05.2016 10:11:06 CRITICAL_PROCESS_DIED 0x000000ef ffffe001`0ad80900 00000000`00000000 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+14e3a0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.3.9600.18289 (winblue_ltsb.160328-1315) x64 ntoskrnl.exe+14e3a0 C:\Windows\Minidump\051516-25765-01.dmp 8 15 9600 138 150 15.05.2016 10:11:41
042816-19328-01.dmp 28.04.2016 22:36:50 CRITICAL_PROCESS_DIED 0x000000ef ffffe001`3da4f900 00000000`00000000 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+14e8a0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.3.9600.18289 (winblue_ltsb.160328-1315) x64 ntoskrnl.exe+14e8a0 C:\Windows\Minidump\042816-19328-01.dmp 8 15 9600 294 472 28.04.2016 22:39:45
041916-23859-01.dmp 19.04.2016 08:43:53 CRITICAL_PROCESS_DIED 0x000000ef ffffe001`23101900 00000000`00000000 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+14e8a0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.3.9600.18289 (winblue_ltsb.160328-1315) x64 ntoskrnl.exe+14e8a0 C:\Windows\Minidump\041916-23859-01.dmp 8 15 9600 294 472 19.04.2016 08:47:04
I saw a post with the same problem on a diffrent site, but none actually answered the problem and the post aged out.
Do anyone have any pointers on how to fix this? Would I have to install ANOTHTER Exchange server and migrate into? This would be very unfortunate..
I've setup a co-exist environment with Exchange 2010 and Exchange 2016.
At the moment mail-flow seems to work with no problems what so ever, and I have migrated two test-users from 2010 to 2016.
SMTP traffic and HTTPS is proxied from the new Exchange 2016 installation - and works fine for the 2010 users behind.
My problem is that when the users are migrated, outlook 2016 is having issues connecting to the new server.
When I open outlook, it still uses RPC/HTTP towards the old server.
If I delete the old profile, and re-create it using autodiscover, it works fine.
I then see MAPI traffic and it hits the new server as expected.
This would cause a problem if I manually have to re-create profiles for all the users in our company..
Does anyone have any pointers?
Edited with more information:
I migrated my own user, and I had my outlook open. I got the message that my box was migrated and that I needed to restart outlook; and so I did! My mobile-phone and OWA works like intended, and it's just my outlook clients acting up. It happened on two of my computers connected to the same mailbox and same user (home and office computer).
When opening my outlook client I get the certificate warning message with the name of my old servers internal name (like: Exch2010.domain.local), and the certificate in use is for our FQDN as mail.company.com.
Second Edit:
I just migrated a test-user from 2010 with outlook closed and tried connecting from an external network. It asked me the question if I wanted to allow https://mail.company.com/autodiscover/autodiscover.xml to edit my settings. I clicked "allow", and nothing happened. The mailbox stayed in a disconnected state and the connection status had one connection which had the status "established". The connection was proxied through mail.company.com and to Exch2010.company.local. I restarted outlook and the same thing happened.
Then I moved the client from the external network, and put it in our internal network instead. Now it gives me the same message "allow this website to configure [email protected] server settings?" but with the local name of the NEW exchange server in an URL format like "https://exch2016.company.local/autodiscover/autodiscover.xml". I allowed and accepted the certificate warning (as it said it was using the local name again - exch216.company.local; which doesn't match the SSL cert).
Outlook is still not operational and is in a "disconnected" state. My own mailbox is "established" but doesn't update.
Out of curiosity I checked the servers by running:
Get-AutodiscoverVirtualDirectory | fl
InternalURL and ExternalURL for all three are blank. I'm not experienced enough to tell if this is correct or not.
For some reason, it seems like the servers are internally announcing their local names instead of the correct "mail.company.com".
I also checked the servers by running:
Get-ClientAccessServer -Identity SERVER | fl
All of them got the AutoDiscoverServiceInternalUri set to "https://mail.company.com/autodiscover/autodiscover.xml".
FQDN for all of them is set as their local hostnames (servername.company.local).
I have no idea what to try next..
Edit number three; as a reply to @Sembee: Hello @Sembee; thanks for your reply. I left them blank and did no changes. I checked the InternalURI for clientaccessserver on all three servers, and they are identical. The Autodiscover-tests complete without problem and have done so since the beginning. Re-configuring a users outlook makes the outlook work again (fresh data from autodiscover). All traffic are passing through the 2016 server for now (afaik), and proxies OK to the 2010 server. None have mentioned any problems. Outlook just isn't working after migrating to 2016 without re-creating the profile and running a new autodiscover.
Fourth edit: When I came in to work today, my own laptop (did not work yesterday/sunday) AND the laptop (did not work on saturday) I use for testing both worked fine. It could be some sort of delayed sync doing this to me? I'm currently setting up another test, to see if it behaves in the same way - and if its possible to time it somehow. Any pointers would be much appreciated.
I have tried moving a primary email address from one mailbox to a new one. Lets call the old adress: [email protected]
I renamed this account, and SMTP addresses to [email protected] and moved the old "[email protected]" address to a new mailbox.
The new mailbox has the name of [email protected] and now "[email protected]" as an alias.
When sending e-mail from external sources, the e-mails appear in the new mailbox. When sending from within our organization from any @company.com address it seems to hit the "[email protected]" even if I type "[email protected]" in the "to:" field.
Could anyone explain why; and how to fix this? When running the Get-MessageTrackingLog and filtering for my own address as sender, I can see my test-mails but the "Recipients" field shows as "[email protected]" this is even if I'm 100% sure I typed "[email protected]".
The change is less than 24 hours old. Could it be some internal address-lists that needs updating? The domain-user for the old account is named Department.old; in the same manner as the primary SMTP address.
I'm trying to discover computers based on IP subnets. The administration server is not part of the same workgroup or active-directory as the clients, so this is the only way to do it.
I can discover about 1/3-1/2 of my computers.
I tried disabling the windows firewall totaly on one of the computers, and it seemed to add itself to the list of unmanaged computers.
When just opening for ICMPv4, so the management server can ping the target client-computer it does not work.
It looks like I'm missing some ports that needs to be open in the windows firewall - but the great internet can't tell me which ports!
Have anyone done this before, and got a clue about what ports I'm missing? Disabling Windows Firewall for all clients, to install the Kaspersky one is not much of a solution.....
I'm trying to get two new Dell R620 servers up and running on 10Gbit interfaces. The servers were delivered with two PCI network-cards for 10Gbit.
At the moment, the network cards installed and reported by iDRAC is:
The integrated card has 4 ports. Each of the other cards have 2 ports each for 10Gbit. The total of availible ports is 8.
Problem number 1: I can only see 7 of the 8 ports in vmware.
Vmnic4 is missing for some reason.
The two NICs that actually links up, is on RJ45 and used for management.
Problem number 2: The switch that one of the vmnics are connected to, got link on 10Gbit towards the server, but vmware clearly states something else!
From the picture above, only two out of three ports that are connected got link. Two RJ45, and one optical 10Gbit are currently wired up.
The switch this is connected to is an Alcatel-Lucent 7210 SAS-M. Status on the port that is connected to this server is as follows:
Port ID: 1/2/2
Admin state: Up
Link: Yes
Port state: Up
How and why would I get an OK on the switchport, but no-go in vmware? Currently running version 5.5 downloaded from Dells software page.
The SFPs have been tested towards the ALU-switch by putting them in an EqualLogic disk-enclosure and checked that both sides links up at 10G. The EQL got the same kind of SFPs and are working fine.
Could this be a network-card firmware issue? Drivers in vmware?
Any pointers would be very helpfull.
We've setup an md3220i SAN to be used against vmware 5.1. When inside a VM on this SAN we tried copying a file multiple times creating multiple/sessions streams. When doing this, it's only the latest stream that runs and all others are paused untill the active one is finished.
Is this something you can change in vmware? or could it be a controller issue/setting? We have 4 luns with 8 paths to each one. If you need any additional information - just ask! :)
Env: 4 Exch 2010 Sp1 hosting mode MBXs, 2 CASHUBs, HLB infront.
This setup runs multiple domains for several different customers. The HLB can be reached at mail.ourhostingdomain.com and is where all the clients connect for anything (as this loadbalances the CAS-servers). When we run autodiscover tests against our own domain which differs form the hosting domain, the WEBSERVER of our primary domain replies with it's SSL certificate. This gives a faulty autodiscover, and warns the users that something is wrong.
I'm running tests with [email protected], and it connects to the HLB as it should on mail.ourhostingdomain.com. Why would the webserver of ourprimarydomain.com reply instead of the exchange/hlb which got the correct certificate?
Ourprimarydomain.com got an _autodiscover SRV record to throw the requests to mail.ourhostingdomain.com (This seem to partially work, as we get connected to the correct server?)
If anyone could explain this behaviour, it would be much appreciated!
(No, there is no A or CNAME for autodiscover.ourprimarydomain.com, just the SRV)
The same thing happens for others on the same platform, and all of them got an SRV record that points to mail.ourhostingdomain.com.
I was wondering if it's possible to use SCCM 2012 in a multidomain environment? We have several domains each in their own forests but with the possibility of network connectivity.
Would it be sufficient to set serveral Active-Directory Forests, with their own set of credentials + their own Boundaries and Boundary Groups?
How is this done best-practice-wise?
The idea is to use SCCM2012 as a tool for keeping servers up to date via WSUS. Would that be doable? Are there issues we could run in to by using this?
I'm having a problem with printers and remote desktop (terminal server).
At the moment, I have set the Session Host settings to not allow default local printer to be set as default in the terminal-session. The opposite was done via GPO earlier. After applying this setting through session host, only ONE user still has a problem with print on the terminal.
This user is the only one having his local default printer connected via USB. His local printers get mapped to the terminal-server, and he is able to select the same printer as default, in his session (which is just like it should be). For HIM and only HIM, the default printer on terminal-server resets every time he logs out and back in.
Could this be related to his USB printer?
Is there any way of bypassing the session host settings for only ONE user? Which in turn will force his locally attached USB default printer to be his default on the terminal server?
Could/Should I apply a specific GPO for this user ONLY?
Any thoughts are most appreciated!
I'm having troubles with my nagios getting it to give me feedback about the ammount of free/used diskspace on the clients it's monitoring.
at the moment, it runs the default check_all_disks!20%!10% and one check_disk!20%!10%!/
Only thing it shows me on the "Service Detail" overview is: Disk OK
It would be very nice to have either the percentage or free/used in the service detail overview.
Is this possible?
If I click the service check - it shows me some numbers in Performance Data. What's this supposed to be?
Edit: Seems like when updating to the newest version of Nagios Core - the information I was looking for, gets displayed.
I'm trying to get Lync 2010 work in my lab environment. I've got a domain controller, a single lync server, a client and a SIP gateway. I've gotten to the part where I have a successfull login from the client to the lync server. I set up a few routes for testing, and made sure the output looks like I want it to when it's passed through Lync.
However, I have a problem when I try to make the call from the client!
The client reports: Operation was unsuccessful. The calling service did not respont. Wait and then try again.
Is this a typical error generated from a misconfiguration in the Lync server, or could this be the a problem with the SIP gateway?
What logs would I dig through, and where do I find them?
Any pointers are much appreciated!
How do I get the SCCM server to direct the clients so they get DHCP, and connect to the SCCM server?
Do I need to have the WDS role installed? Is this a requirement?
When I try to install FEP2010 combined with SCCM R3 and SQL 2008 STD, I get this error:
Error: Setup cannot determine the SQL Integration Service version. Microsoft Forefront Endpoint Protection 2010 requires Microsoft SQL Server Integration Services 2005 Enterprise or Standard edition with Service Pack 2 or higher or Microsoft SQL Server Integration Services 2008 Enterprise or Standard edition or higher. Make sure that the component is installed, running and auto-started on server server.domain.ok.
The services are started, and set to auto-start with the local system account.
Any pointers on how to solve?
What would the setup look like if my network looks like this:
192.168.1.10 - Exchange server
192.168.1.1 - FireWall / Internal
10.0.0.0 - FireWall / External (imaginary IP..)
20.0.0.0 - mail.myisp.com (SMTP)
I can now successfully send mails through this setup by using an SMTP connector. This works both on the local domain and to outside addresses.
The problem is recieving mail!
What would I have to do to make that happen?
What kind of DNS records would I have to make to fit this setup?
The network only has one external address.