You are not logged in.
dsadd ou (I cannot post link)
Something changed and dsadd ou cn=x,dc=y,dc=z doesn't work on Windows 2016 , instead of it we have to use
dsadd ou ou=NewOU,dc=Domain1stPart,dc=domain2ndPart
I don't remember how it was before, but probably cn= was correct.
Offline
Thanks pawel, I've fixed that now.
Offline
On the shutdown page. All the options marked "Windows 10" were already added since Windows 8 / 8.1.
Exceptions are: /soft and /fw those seem to be missing in 8 / 8.1
Last edited by Mastonas (26 Jan 2019 05:08)
Offline
Fixed now, thanks Mastonas
Offline
The description of Write-Warning cmdlet (Powershell) is "Write a string in reverse video to the display", and "reverse video" has inverted colours (grey text in black background).
Offline
^ Thanks I fixed that colour and added a couple of extra examples to the page.
Offline
windows server 2003 resource tool kit is no longer available for download on microsoft sites.
I've found a version here: http://ftp.unicamp.br/pub/apoio/winserver2003/rskt/ - looks legit.
May be could be backed up here.
Offline
It is on Archive.org, so I have linked to that version it's likely to stay up for longer. Thanks for the heads up.
Offline
Some new utilites with the latest windows 10 updates:
logoff on the help page shows different interface than the now available in windows - looks like also a VM support has been added:
LOGOFF [sessionname | sessionid] [/SERVER:servername] [/V] [/VM]
sessionname The name of the session.
sessionid The ID of the session.
/SERVER:servername Specifies the Remote Desktop server containing the user
session to log off (default is current).
/V Displays information about the actions performed.
/VM Logs off a session on server or within virtual machine. The unique ID of the session needs to be s
pecified.
changepk (https://docs.microsoft.com/en-us/window … n-upgrades) :
Upgrade using a command-line tool
You can run the changepk.exe command-line tool to upgrade devices to a supported edition of Windows 10:
changepk.exe /ProductKey <enter your new product key here>
You can also upgrade using slmgr.vbs and a KMS client setup key. For example, the following command will upgrade to Windows 10 Enterprise.
Cscript.exe c:\windows\system32\slmgr.vbs /ipk NPPR9-FWDCX-D2C8J-H872K-2YT43
nmbind - looks useful for managing network bindings - looks pretty similar as interface to nvspbind (https://gallery.technet.microsoft.com/H … d-cf937850) but supported and with less options.
I have no idea with which build it has been introduced - file signature points to 10.0.1904 but it was not announced in the release info.
Usage: nmbind [option] [NIC|*] [protocol|*]
Options:
/n display NIC information only
/u unbind switch protocol from specified nic(s)
/b bind switch protocol to specified nic(s)
/d disable binding of specified protocol from specified nic(s)
/e enable binding of specified protocol to specified nic(s)
There are other command lines too , but some of them are too specialized and some I haven't check yet.
Offline
many thanks once again npocmaka, I have now updated those pages.
Offline
I think the page about ANSI colors should be redone to explain all the things that VT100 sequences can do, or at least mention that 24-bit colors are now fully supported by the Windows Console.
(Unrelated: how can I get the authorization to post links?)
Offline
Hi ThePirate42
Good idea, I just added a short paragraph about this to the color page and the ANSI colors page.
https://ss64.com/nt/syntax-ansi.html
Also I have upgraded your forum account.
Offline
Good idea, I just added a short paragraph about this to the color page and the ANSI colors page.
https://ss64.com/nt/syntax-ansi.html
But ColorTool.exe is not necessary to take advantage of 24-bit colors! It's much simpler to use the VT100 sequences described here.
The documentation says that "For these extended colors, the Windows Console will choose the nearest appropriate color from the existing 16 color table for display", but it isn't true, if you use this sequences with a version of the Windows Console that supports 24-bit colors you will get the wanted RGB color.
Last edited by ThePirate42 (05 Dec 2020 15:52)
Offline
Simon Sheppard wrote:Good idea, I just added a short paragraph about this to the color page and the ANSI colors page.
https://ss64.com/nt/syntax-ansi.htmlBut ColorTool.exe is not necessary to take advantage of 24-bit colors! It's much simpler to use the VT100 sequences described here.
The documentation says that "For these extended colors, the Windows Console will choose the nearest appropriate color from the existing 16 color table for display", but it isn't true, if you use this sequences with a version of the Windows Console that supports 24-bit colors you will get the wanted RGB color.
Ah thats good to know, have updated the page again now. I still haven't had time to actually play with these new colors properly.
Offline
Ah thats good to know, have updated the page again now. I still haven't had time to actually play with these new colors properly.
I hope you will find the time, VT100 sequences are amazing! They can do much more than color, for example, with this code you can display a loading message that will disappear after the loading has been completed:
echo Loading...
rem
rem Stuff like configuration parsing, dependency check...
rem
<nul set /p ="%ESC%A%ESC%[2K"
You can also use an alternative screen buffer, disable scrolling in some regions of the console and much more!
Last edited by ThePirate42 (05 Dec 2020 17:28)
Offline