If you have been following the recent Turing Robotic industries ‘Turing Phone updates, you may have received the below email:
|
|
|||||||
|
Click on the start menu, or press the WIN key, then simply type (win vista+) CMD
Right click on cmd.exe and select, run as administrator 
If that does not for some reason work, or you cannot get into your start menu, try pressing WIN + R and typing CMD, then enter:
runas /noprofile /user:Administrator cmd
This will prompt you for your admin password
Below are the quick steps to take if you are in the situation where you need to create a new pc user from command line. The example below is for creating a user named nick, with admin privileges.
Open up an elevated command prompt:
Type the below, exchanging *nick* ad *password* with your own username and password.
net user /add *NICK* *password*
To give this user admin privileges;
net localgroup administrators *NICK* /add
To Disable or Enable an account from a CMD terminal (command prompt)
Net user Nick /active:no
To re-enable the account :
Net user Nick /active:yes
There are 2 ways to find the folder location of AppData on a PC, and to check appdata path.
The first method uses the simple $env: command. This command has long been used by C# users to make multi platform software, in the case where your AppData or any other environmental variable may be living somewhere other than the normal factory set location.
Simply open up powershell and type:
$env:APPDATA
Method 2 is basically doing the exact same as above, but this time using a call and answer approach:
Get-Childitem env:APPDATA | %{ $_.Value }
Below are some extra $env: variables that you may find useful;
Name Value ---- ----- TEMP C:\DOCUME~1\bob\LOCALS~1\Temp SESSIONNAME Console PATHEXT .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.PS1;.PSC1 USERDOMAIN WINGROUP PROCESSOR_ARCHITECTURE x64 SystemDrive C: APPDATA C:\Users\bob\Application Data windir C:\WINDOWS USERPROFILE C:\Users\bob
After a batch of updates over the weekend, Windows is now providing more info on the long awaited FREE windows 10 upgrade
The popups, now appearing on some windows 7 and 8 PC’s are causing quite a stir. With some people on reddit calling it both ‘intrusive’ and ‘malware-like’
It would appear that it is KB3035583 that installs this notification, but that requires Windows 7 SP1 or Windows 8.1 to function correctly, at the bottom of the article we have included a step by step guide in forcing this update in order to be able to reserve your own copy of Windows 10
Below, the sirst 5 screens, then taking you through to the final offer, of ‘reserving Windows 10’
If you are still looking to get a hold of the update supplying this notification then Reddit user FearGX_ explains that you can force the update to do its thing. We’ve reformatted his instructions below.
Again, this will only work if you’re running a legitimate copy of Windows 7 SP1 or Windows 8.1, have KB3035583 installed, and have all the latest updates.
Without going into detail about how this process works, or what it does, If you have just migrated a new Server and are ready to make it the live master for the forrest and domain, simply open up a command prompt (CMD) and enter the following lines in one after the other;
Ntdsutil
Roles
Connections
Connect to server *New Server Name*
Q
Seize infrastructure master
Seize naming master
(if success – continue to the below)
Seize PDC
(Server “*Server Name*” knows about 5 roles)
Seize RID master
Sieze schema master
Q
Finito. (<– dont type that!)
Because an Active Directory role is not bound to a single DC, it is referred to as a Flexible Single Master Operation (FSMO) role. Currently in Windows there are five FSMO roles:
Schema master
Domain naming master
RID master
PDC emulator
Infrastructure master
And that is your FSMO roles all transferred over using simple command line. Please keep your eyes peeled for further posts looking deeper into each of the FSMO Roles,
Here is a quick way to check the health of a PC joined to a domain controller. This is very useful if you need to do a quick check in the first instance of diagnosing a trust relationship issue.
1) Open up a powershell console
2) Type or copy/paste the following, replacing the *dc mane* with your networks domain controller
Test-ComputerSecureChannel –Server *dc name* -Verbose
3) check results, If it comes back with red text it is a pretty good indicator that there is some form of problem going on, however if it returns “The secure chanel between ‘*’, ‘*dc name*’ and ‘*domain*.local’ is alive and working correctly” then you can continue investigating your problem knowing that the PC is nice and safely connected to the domain.
For troubleshooting Trust Relationship issues with a Microsoft Domain, please keep your eyes pealed for part 2
If you have ever been in the situation where a time server or an old server will just not keep in sync, perhaps due to a CMOS battery error, or simply old hardware, then this cmdlet is for you.
Open up a command prompt and copy/paste the below:
w32tm /config /manualpeerlist:”0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org”,0x8 /syncfromflags:MANUAL
w32tm /config /update
net stop w32time
net start w32time
w32tm /resync /nowait
All that this is now doing is setting the clock to update automatically from a web time server, the servers we are using are the public pool 1, 2 and 3 at ntp.org
We stop and start the time services, and then tell it to resync with the new settings.
