Search the Community

Hi, I've no doubt this question has probably been asked before so I apologise in advance if I am doubling up! Can anyone give a list of the definitive services required to be active / disabled on a remote PC in order to avoid this response: The machines in question are behind an enterprise firewall, as is the host, so Windows Firewall is turned off. Remote Procedure Call (RPC) - auto Remote Registry - auto Windows Remote Management (WS-Management) - auto Windows Management Instrumentation - auto These are the obvious enabled services, but I can not get an answer from any Microsoft website as to what needs to be set for remote administration. The error code seems to be very general, with lots of reasons for it. Not all related to remote access. Currently, with the above set, some Windows 7 machines work and some don't, hence my confusion. Any thoughts would be appreciated. Cheers,

I'm trying to deploy Forefront from Server 2008 to Windows 7 clients using the MOM 2005 Administrator Console. I've added port exceptions (tcp and udp) 1270, 135 and 445, on the server and client, but always get an error: If I turn off the client firewall, it installs fine. The most detailed page addressing this problem (on winserverkb.com) suggested adding the program exception: but this didn't help either. Has anyone encountered this and know what ports to open/programs to allow?

Hey all, We're looking into increasing our power in our colocation from 120V 20 amp to 120V 30 amp so that we can add more equipment. When looking for PDU's it seems that a PDU that will take a 120V input and output 30 amps is uncommon. Most 30 amp PDU's seem to take a 200V+ input. If we got a PDU that lists a 200V or 208V input and output, and plugged it into a 120V circuit, what would be the outcome? Would that be ill-advised? Thanks! -Scott

Asking here before raising an MS ticket, but has anyone published Exchange 2013 through Forefront UAG 2010 SP3 (with Rollup 1) and limited it to NTLM authentication? For me, it works for everything except passing RPC through UAG which breaks OA. I followed this guide without issue: Download Publishing Outlook Anywhere Using NTLM Authentication With Forefront TMG or Forefront UAG from Official Microsoft Download Center The Remote Connectivity Analyser throws an error at: Attempting to ping RPC endpoint 6001 (Exchange Information Store); The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process. Telnet to the 6001 port internally works fine. I am hopeful someone is running a similar config and I can compare key components.