Reputation
43,142
Next tag badge:
399/400 score
153/80 answers
Badges
24 114 227
Impact
~4.6m people reached

7h
answered Big Trouble with (I think) Outlook X500 addressing
12h
comment LAN gets stuck sometimes
Looks like a dodgy (and probably very cheap) switch. Replace it.
13h
revised Service dependency on Active Directory
added 10 characters in body
13h
comment MS-DOS attrib +s 'path not found'
Also, see the edit for another test more similar to your actual situation. As you can see, everything seems to work as expected.
13h
revised MS-DOS attrib +s 'path not found'
added 576 characters in body
13h
comment MS-DOS attrib +s 'path not found'
Same result on Windows 7 and 8.1, and I even tried it on an old Windows Server 2003 machine, it still worked perfectly; Unicode has a long history of being supported on Windows. Your problem must lie elsewhere, not in the file name.
13h
comment Lync Certificates
But they could happily use private certificates for the external web services: the reverse proxy is the only server which is actually Internet-facing, thus you could put the public certificate there and use private certificates on the actual servers; the RP will proxy the requests to the internal servers, and external clients will only see the certificate on the RP.
13h
comment Lync Certificates
Anyway, you seem to have four servers: two front-ends, one edge and one reverse proxy. And yes, if you have two front-end servers in the same pool, they should use the same certificates for the same roles.
13h
comment Lync Certificates
"The Front End server is is the main server. The Reverse Proxy and Edge Servers are VMs on the Front End." This is just wrong on so many levels...
13h
comment MS-DOS attrib +s 'path not found'
Same behavior with folders. And please stop talking about "icons", those are files and filenames :) their content is not relevant to applying attributes to them.
13h
revised MS-DOS attrib +s 'path not found'
Retagged
14h
answered MS-DOS attrib +s 'path not found'
14h
answered Service dependency on Active Directory
15h
answered Shared access to iSCSI target
1d
comment Exchange Hybrid no longer needed
Anyway, we are going way out of scope here; let's stop it at "if you want DirSync and your Exchange management to not be a Royal Pain, you'll need an on-premises Exchange, which will need to be fully configured and working even if it's not going to actually host any mailbox". If you have further questions about specific issues, just ask new ones.
1d
comment Exchange Hybrid no longer needed
There are lots of documentation around, and it depends on your implementation; also, the hybrid link isn't used exclusively for mail flow, but also to actually have the two Exchanges (on-premises and online) talk together; DirSync is not enough.
1d
comment Exchange Hybrid no longer needed
I personally don't know of any tool to manage Exchange-related attributes other than Exchange itself or plain low-level LDAP editors.
1d
comment Exchange Hybrid no longer needed
I don't know if it's possible to remove a hybrid Exchange deployment and then re-establish it, but I'd advise against trying; just set up the new server in the same AD forest, transfer all that is required as per standard Exchange move process and then remove the current one; you'll probably also have to change a connector or two.
1d
answered Exchange Hybrid no longer needed
2d
accepted Simplest way to move a small public folder to Exchange Online?