a 6ya expert can help you resolve that issue over the phone in a minute or two.
best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
the service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones).
click here to download the app (for users in the US for now) and get all the help you need. goodluck!
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
psexec in fact does run as the user
running the command window that initiated the command. I use this
command almost daily to run either command shells, batch or vbscripts,
etc on remote computers. I've learned some about its behavior from
watching the results.
Basically, psexec copies itself to the
ADMIN$ share on the remote computer. It then installs a service on the
remote computer, and runs that service, which is the copied file. This
then executes the command that you specified in the psexec command line.
with that in mind, the user running psexec from the command line needs
to have admin rights to the remote computer. You can bypass this
requirement by using the "-u" parameter, and specifying a
domainname\username. Domainname can be the remote computer's name if
you have a local user. By putting in just the -u parameter, you'll then
be prompted to type in the hidden password.
Once running on the remote computer, psexec will function in one of three ways: 1 - If no special parameter used, will run in the same user account as the person initiating the psexec command. 2 - If the "-u" parameter is used, it will run as that user. 3 - If the "-s" parameter is used, it will run as a local system account In either of these 3 cases, you first have to have admin rights to use the ADMIN$ share and install a service.
When domain membership is broken on a computer, I'll frequently use a command line like this: psexec -u COMPUTERNAME\Administrator \\COMPUTERNAME cmd.exe
will allow me to have local admin rights by connecting to the remote
computer as the local administrator account. It will also run the
cmd.exe command as the local admin account.
LogMeIn is not officially supported within Google Chrome, but the
Mozilla Firefox version of the plugin has been verified to work in
Google Chrome with the help of the following script: <a href="http://userscripts.org/scripts/show/53796">http://userscripts.org/scripts/show/53796</a><br />
For XP put script in:<br />
"C:\Documents and Settings\YOURUSERNAME\Local Settings\Application
Data\Google\Chrome\User Data\Default\User Scripts"
For Vista and 7 put script in:<br />
To use, you must run your browser's exe with the parameter
<li>Right-Click on the Google Chrome Shortcut.</li>
<li>In the Shortcut Tab, change the Target to "C:\Users\YOURUSERNAME\AppData\Local\Google\Chrome\Application\chrome.exe --enable-user-scripts"</li></ol>
Now the LogMeIn plugin can be installed in Google Chrome from here:
Using two domains for example Domain X and Domain Y.
You can create a two-way trust with domain-wide authentication.between the two domains if they belong to the same organisation depending on the imformation that you want to share or use between the two domains .you do this on an established domain controller for each domain.
.On the server where you have domain controller for example on Domain X ,log on as an administrator then go to >Start >Administrative Tools >Active Directory Domains and Trusts.then Right-click on Domain X, go to > Properties. >click on "Trusts" tab. then > New Trust. click - [Next].
In the name field type the second domain to trust thats domain Y, in this case then click >next to continue
then Select the Direction of the Trust. either two way trust or one way but in this case its a two way then Click [Next].
In "Sides of the Trust", select the "This domain only" bullet. then [Next].
Set the Authentication level to "Domain-wide Authentication". then [Next].
you will be prompted to Enter a Trust Password twice. also Remember to make it strong enough to comply with password criteria in your domain security policy.
Click [Next] - [Next] - [Next].
Select the "No" bullet to the Outgoing Trust Confirmation - [Next].
Select the "No" bullet to the Incoming Trust Confirmation - [Next].
Click [Finish] - [OK].
Log off of DomainX ,
ON THE SECOND DOMAIN (DOMAIN Y) YOU PERFORM THE BELOW STEPS
Then .Login to DomainY using Administrator account.
go to > Start > Administrative Tools ->Active Directory Domains and Trusts.
Right-click on Domain Y, and select Properties. click on "Trusts" tab. Click the [New Trust...] then [Next].
in the Name field type domain X to indicate the domain to trust, then click [Next].
Select " the Direction of the Trust. in this case its a two way trust then Click [Next].
In "Sides of the Trust", select the "This domain only" bullet. Tthen Click [Next].
Set the Authentication level to "Domain-wide Authentication". then Click [Next].
you will be prompted to Enter a Trust Password twice.dont forget to use the same Trust Password that you used previously in the step above then Click [Next] - [Next] - [Next].
Select the "Yes" bullet to the Outgoing Trust Confirmation - [Next].
Select the "Yes" bullet to the Incoming Trust confirmation - [Next].
Thanks for the background info, this makes it easier for me to see what you need.
You need to disable your guest account if you havnt already done so.
The user is logging on with a cached version of the logon information, this is useful for when the server goes down but not in your case as you need to prevent this.
Another worrying aspect is that you allow all your users to log on using the same password. Very bad from a security aspect anyhow. It is better to change at least every 30 days. If they moan they will get used to it soon enough.
Go into group policy again and computer configuration>windows settings>security settings>local policies>security options and look for interactive logon:number of previous logons to cache - set this to 0. If the domain controller is not available and the logon info is not cached they cannot logon to domain.
Group policy can be overruled at the client end if they have admin priviledges so you may have to set this on the client pc also. But you need to test to see if it is required there. I have not used that particular policy but it should be ok just on the server. Your users dont have admin rights do they? Anyway good luck. You can set this by applying it to an OU or domain wide but if you want to target just this one pc then maybe if you put it in its own ou and apply it just there.
You need to create new policies rather than modifying the domain one and keep each policy for specific purposes so that applying them to ou's is easier, ie internet options policy, firewall policy, working hours policy etc.
You should make sure that you have administrative previlges to do this.
Some programs may have prevented the network service from being disabled.
This can also be caused by a virus too. So you also install and run a
full system scan. Don't rely on a single antivirus. try different one
if one doesn't solve the problem.
Some worms prevent the networked systems to be controlled by users of the administrative groups.
also remember that most of today's networks are equipped and monitored
with network monotoring ultilities. some of these also acts as
firewalls too. This may prevent you from disabling the local area
If nothing works at all, just pull the network plug (RJ45). will
disable the network connection. this way the appliaction that is using
the connection is likely to display some error message. if this is a
freindly application change the configuration settings of this
application so that you could control the lan connections.