Windows 3.0 and Windows NT 3.5, I can extract the best from this platform both on the desktop performing the most diverse Deployments and on the Server in the following scenarios:
- Terminal: Windows Terminal(DOS) or PowerShell;
- Windows Editions: Windows Core (cmd.exe only) and GUI editions:
- Windows Core: It was a single experience, installing database and Hypervisor. It was interesting to learn, but it's not like Linux, the drivers are installed by terminal and must support .inf files and not need GUI. Therefore, this system is not used anywhere, they are generally approved hardware to work properly;
- Windows Servers: Apart from the licensing issue, they are all the same in the way they are managed, but differing in resources between them;
- Windows Terminal: The RDP protocol was created in partnership with Citrix and I really like this type of environment for the flexibility and security it provides.
- merge remote tree nodes because unfortunately I never needed to use this feature. I've also worked on base recovery;
- Policies: Proficient in managing this resource with an emphasis on security:
- I implemented strict security that prevented users from running popular programs without authorization;
- Prevent the use of mass devices (cdrom, flash drives, external hard drives) in authorization;
- Virtualization: Microsoft Hypervisor and terminal(ssh). Windows includes a hidden ssh server;
- With the addition of the WSL2 feature we can finally take advantage of linux tools on Windows;
- Languages(-scripts) for server. In this environment I am familiar with .vbs and .cmd scripts, not limited to basic resources, but with the purpose of maintaining installed services:
- I often create my own backup and cleanup tools using vbs/cmd;
- Use of vbs/cmd compilers, although uncommon are used more to camouflage script content;
- Use of RunAs. Unfortunately, one of the most common problems in multi-terminal environments is running programs with special privileges, knowledge in the area of programming and scripting using runas allows me to create solutions that allow users to run legacy programs or request special privileges using a common account:
- Using a multi-terminal environment it is possible to create kiosks for programs that require an administrator account, although this can be granted as a last resort, the developer will only use the program and not share the desktop to have free access to files;
- ANSI-2002 SQL language. Any database compliant with this standard will be familiar to me.
- Databases MSSQL Server (administration and development): I've known him since his product was a joinventure with Sybase, MSSQL 6.5. I have already recovered corrupted databases and often write scripts to handle its backup which involves cmd and SQL DML/DDL/PSQL languages.
If I don't have all the necessary skills, be patient because I learn fast.