I think there's abig difference in Server 2012 R2 DA and the original implemenation of DA>
________________________________ John Marcum Sr. Desktop Architect Bradley Arant Boult Cummings LLP ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Linkey, Mike Sent: Thursday, December 05, 2013 1:20 PM To: [email protected] Subject: [mssms] RE: Direct Access & ConfigMgr 2012 I am definitely not IPV6 savvy at all. I know IPV6 is involved, but that is it. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Lutz, Ken Sent: Thursday, December 05, 2013 8:49 AM To: '[email protected]' Subject: [mssms] RE: Direct Access & ConfigMgr 2012 Mike, That makes sense. It does raise another question. When I look at the properties for the workstation I see the IPV6 address that matches the IPV6 that I get when I ping the workstation from the DA server. DNS is also showing this same IPV6 address for the workstation. When I try to ping the workstation from my desk I get "Ping request could not find host". I get the same response from the site server. Couldn't one reason for that be a lack of IPV6 routing? Wouldn't remote control then work if the address was resolvable? Wouldn't the DA server then complete the route via the NATed address? I am seeing two IPV6 addresses in ConfigMgr for this workstation. One is for 2001:0000 and the other for FD9D:723D. Isn't one the inside address and the other the outside address? I must admit that I don't know very much about IPV6. Thanks, Ken ... From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Linkey, Mike Sent: Thursday, December 05, 2013 5:58 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Direct Access & ConfigMgr 2012 We have this setup. I don't believe remote control will work since the IP address on the client is more than likely NATed by the provider. DA proxy's through the DA server, so the clients are not using IP addresses on the local network, but appear that way. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Lutz, Ken Sent: Wednesday, December 04, 2013 4:44 PM To: 'SMS List' Subject: [mssms] Direct Access & ConfigMgr 2012 We are just starting to play with DA, and we have it working with Windows 8/8.1 workstations. I have the ConfigMgr client loaded on a workstation connected via DA. I am in the very early stages of testing and wanted to know if anyone had anything that they needed to do to get everything to work? Right now I am looking at Remote Control. I can't connect to the remote workstation and I think the problem is with IPV6. My internal network isn't set up to support IPV6 yet. I am not able to ping the workstation when it is connected via DA unless I ping it from the DA server. From the site server I can't ping the workstation. I see IPV6 addresses for it in DNS. The workstation properties in ConfigMgr show both an IPV4 and IPV6 address. There is no IPV4 address in DNS, so I'm thinking it got the IPV4 address when it was connected on the internal network to get the DA GPO loaded. To get ConfigMgr to work with your DA workstations did you have to do anything special? Have IPv6 setup for your internal network? Thanks for the help! [cid:[email protected]] Ken Lutz Senior Systems Administrator Information Systems Department Spokane County 815 N. Jefferson Spokane, Washington 99260 ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer.
<<inline: image001.png>>
