Hello, 

Is there any chance the workstation communicate to MP Server once I remove the Workstation record from AD ?

More Details : 

Months ago in the workstation SCCM 2012 Client installed that time workstation in Domain , Now if i removed from AD still any chance to communicate to MP Server ?

If you mean to ask that a client has to be domain joined to communicate with ConfigMgr, then the answer is Yes. ConfigMgr can also manage workgroup clients. Of course it's important that the client can resolve the MP's name and the client is still able to make that conne

I agree with all off you ...!

But here my concern is The workstation communicated with MP Server but the machine not in AD...!

If machine not in AD still communicated when the IBCM Server existed but in my case there is no IBCM Server.

Example :

Workstation Name : Win7client joined in ABC.com AD and installed SCCM 2012 Client

After few days I may delete the Win7client from ABC.com AD then 

Is there any chance to communicate to MP Server ? 

The protocols used by a workgroup system are the same as those joined to the domain.

I still don't understand where the confusion lays here. What are you confused about?

As mentioned, ConfigMgr doesn't care about AD domain membership for clients so there's no difference between a client joined to a domain and a client not joined to the domain.

Not sure what you're asking about with IP Boundaries and Same Network?

Peter, 

Based on what protocol the Workgroup communicating ConfigMgr ?

IP Boundries ? 

Same Netwrok ?

Can you please spoon feed me about this confusion 

Ok please give me chance to explain one more time .....!

Example : 

The win7client1 computer joined AD and communicating to regional SCCM 2012 MP Server . 

One day I was deleted the record from AD , make sure here I didn't change any settings in client machine .

after 7 days the client came into network the same showing in MP Server that this client was last communication and time 

Can you please clarify here as per my example

We've answered that already multiple times. The client doesn't care about or depend upon AD so there's nothing to clarify.

AD is a directory typically used for authentication an authorization. ConfigMgr does *not* use AD for this at all to manage clients. ConfigMgr uses certificates for authentication and authorization of the clients. This has *nothing* to do with protocols, IP boundaries, or networks so still have no idea why you're asking about those. Clients only need to be able to communicate with the MP to perform their function.

So once again, we've answered this question.