Network domain and laptops

[totalPCTechs]

OK I'm not the greatest at networking but I have a client who wants to put his laptop on a domain. Problem is he leaves the office a lot and he has to be able to have access to the laptop while away from the domain. How would I go about solving this? Thank you in advance!! Computer is running windows 7 pro of course.

Sent from my SAMSUNG-SGH-I777 using Tapatalk

 

[DSep]

even when connected to a domain, the user can log in locally on the machine. If his files need to be synced, between the two profiles, you might consider some sort of file syncing software like syncback.

 

[dbdawn]

OK I'm not the greatest at networking but I have a client who wants to put his laptop on a domain. Problem is he leaves the office a lot and he has to be able to have access to the laptop while away from the domain. How would I go about solving this? Thank you in advance!! Computer is running windows 7 pro of course.

Sent from my SAMSUNG-SGH-I777 using Tapatalk

Cached domain credentials. Also if he has files (i.e. My Documents) on a network drive and would like access to them off the domain, you will have to setup offline files. You can choose to sync offline files on log on and log off of the user.

After a successful domain logon, a form of the logon information is cached. Later, a user can log on to the computer by using the domain account, even if the domain controller that authenticated the user is unavailable. Because the user has already been authenticated, Windows uses the cached credentials to log the user on locally. For example, suppose a mobile user uses a domain account to log on to a laptop that is joined to a domain. Then, the user takes the laptop to a location where the domain is unavailable. In this scenario, Windows uses the cached credentials from the last logon to log the user on locally and to allocate access to local computer resources.

http://support.microsoft.com/kb/913485

 

[YeOldeStonecat]

even when connected to a domain, the user can log in locally on the machine. If his files need to be synced, between the two profiles, you might consider some sort of file syncing software like syncback.

There is no need for this clunkiness and confusion for the customer of multiple log ins.

As DBDawn mentioned above...the operating system will "cache" domain credentials. The first time you log onto a computer set up on a domain, you log in as the domain user, it pulls down a token file and stores it locally. In the future, when the user logs in...at first the OS will try to contact the DC where the domain user account it held...but if it times out looking for it...it will fall back to this local cached credentials file for authentication and log in.

The laptop I'm typing from right now..from the comfort of my couch at my house...is setup on my domain at my office..yet I could log in fine.

 

[Encrypted Existence]

Thanks for the info Stonecat...I did not know it was that simple.

 

[onetech4all]

As DBDawn mentioned above...the operating system will "cache" domain credentials.

- that's right it will cache it.

Correct me if I am wrong, but it needs to be connected back to the domain every 30 days or 90 days, I am forgetting, for kerberos not to "break".

 

[YeOldeStonecat]

Correct me if I am wrong, but it needs to be connected back to the domain every 30 days or 90 days, I am forgetting, for kerberos not to "break".

It is indefinite by default....I've had a laptop going for a couple of years after I permanently shut off a server at home.

 

[DSep]

There is no need for this clunkiness and confusion for the customer of multiple log ins.

As DBDawn mentioned above...the operating system will "cache" domain credentials. The first time you log onto a computer set up on a domain, you log in as the domain user, it pulls down a token file and stores it locally. In the future, when the user logs in...at first the OS will try to contact the DC where the domain user account it held...but if it times out looking for it...it will fall back to this local cached credentials file for authentication and log in.

The laptop I'm typing from right now..from the comfort of my couch at my house...is setup on my domain at my office..yet I could log in fine.

Correct. I just throw out solutions that could work... not really a networking guy, though.