Posts Tagged ‘microsoft’

Daaaaamn. Now that’s a good news. Hiren’s made a new bo0table carrier for new Windo0ze. /dev/me already d0wnloading.

But actually you may also want to lo0k @

Let’s say that you have to manage 60 Windows Servers with separate credentials, IP addresses, etc. It is heavy to open them one-by-one or even by using RDP Manager.

There’s one simple app+script: use RDP Plus from (VirusTotal free).

And use this little code to a simple *.bat file:

C:\to0lz\rdp.exe /v:server1 /Domain:mydomain /U:user /P:pazw0rd
C:\to0lz\rdp.exe /v:server2 /Domain:mydomain /U:user /P:pazw0rd
C:\to0lz\rdp.exe /v:server3 /Domain:mydomain /U:user /P:pazw0rd
C:\to0lz\rdp.exe /v:server4 /Domain:mydomain /U:user /P:pazw0rd


First of all, you’ll don’t find this piece of sh1t in Add/Remove Programz in Control Panel so basically it must be manually deleted from teh Windows Registry. Type regedit in Search Box. Go to HKEY_CLASSES_ROOT\Installer\Products\ and search for string starting with 00005. All Offize products start with 0000X. Delete this and viola, now you can install your Office add-on/expl0it. REMEMBER! Plz backup your registry first before deleting this item.

When creating a new Active Directory structure or you’re adding a new site, it is quite important decision to make to choose a correct domain name because there could be a lot of errors and software repercussions on the topology infrastructure if something could go wrong. This is of course a business decision influenced by organization needs, so sometimes this task can be heavy. Also administrators don’t have day experience on this task, so there is a scary factor.

The task is quite easy to achieve IF everything in the network is correctly configured (especially DNS, trusts and GPO).

1. Main prequisite is to test DNS servers and domain controllers between the sites. To achieve this you simply can do from both servers:

nslookup [servername1]

2. For the rename for the sack of safety you should remove the trusts between the servers or just make in one-directional from the Active Directory Domains and Trusts panel.

3. If you aren’t quite sure if the structure is totally valid there’s an easy command to do so. This command is also the main command for changing the Domain names. An xml file will be created that lists the current domain information, namely ForestDNSZones, DomainDNSZones and NetBios name. The file is in %sysdrive%\Users\[user_that_issued_command], e.g. C:\Users\Administrator\

rendom /list

4. Open the DomainList.xml and rename all names for ForestDNS, DomainDNS and NetBios. Save it to the same location, I mean like this:


Change it to:


5. You can verify your changes by typing command

rendom /showforest

6. Now that we feel more confident, it is time to upload the modified xml to our domain controllers using the command:

rendom /upload

From this place a Windows firewall should be turned off because there could be a couple of errors showing.

7. If there are no errors you can go to this command and verify the domain name change radiance:

rendom /prepare

8. From this point you will type last command, but wait, the domain controllers will restart and the same time:

rendom /execute

9. You should reboot the servers twice, because… this is Microsoft, and sometimes gpupdate /force is quite annoying. Otherwise it will continue to use credentials from the old domain and will no longer be able perform changes on the new domain. By the way, all member servers and workstations will need to be rebooted twice to reflect the change, but not yet!

10. Renaming the GPO’s:

gpfixup /olddns: /
gpfixup /oldnb:OLD /newnb:NEW

11. Renaming computers:

netdom computername /
netdom computername /

12. NOW is the time to reboot workstations and log users in the new manner. AFTER this operation you can do:

rendom /clean

13. Hint: if something doesn’t work – always rebo0t twice…

Pain in the ass Microsoft… really?

If you want to migrate, connect, transfer, whatever to do between two domains there’s an captain obvious that says “create a trust”.

OK. If you want to create a trust between forests of Active Directory, you would just go to Active Directory Domains and Trust and create a trust… yea, but not with Microsoft.

Ok, stop shitty talk, I’ll just write how to do this:

1. If it is not working the problem accuratelly lies within the DNS configs.
2. For creating a relation between 2003 and 2012 the DNS’s must have a Conditional Forwarders configured.
3. For 2003 go to DNS > $domain > Properties > Forwarders > Add 2012 domain name and IP.
4. For 2012 go to DNS > Conditional Forwarders > New Conditional Forwarder > Add the 2003 domain name and IP.
5. Diagnose with nslookup is everything correct by typing on both servers like:

nslookup $domain2003 -type=ALL
nslookup $domain2012 -type=ALL

6. If everything is correct you can now create a trust.
7. Active Directory Domains And Trust > $domain2012 > Properties > Trusts > Add new trust.
8. Place a $domain2003 DNS name > Next > Forest trust > Transistive > Two-way *or not.
9. If you selected two-way it will automatically shown on the 2003 Server if placed correct credentials in the Trust Wizard tab.
10. You will try to validate these credentials on both servers to save the routing information and it will fail… Microsoft.
11. Just rebo0t both servers.
12. Done.

Introducing Microsoft System Center 2012 R2 Technical Overview.


Zainstalowałem prekonsumencką wersję Windows 8 32-bit. Pierwsze odczucia – Microsoft zmierza w kolaborację komputerów mobilnych (zwanych telefonami komórkowymi dawniej) ze stacjonarnymi (przenośnymi). Wszystko jest maksymalnie uproszczone od strony GUI użytkownika, a administracyjne zagwostki informatyczne są poukrywane i… słusznie. Interfejs łudząco jest podobny do smarfonowej modyfikacji androida, które nazywa się Windowsem Mobile. Co ważniejsze – brak menu start, zamiast tego w rogu jest ukryta ikona przełącznika okna aplikacji. Wygląda ciekawie, pracuje szybko. Jestem nieco zaskoczony pozytywnie, ale dobrze wiemy, że co drugi system MS jest nieudany, a skoro siódemka była ok… .

Dla chcących popróbować swoich sił podaję uniwersalny klucz licencyjny: NF32V-Q9P3W-7DR7Y-JGWRW-JFCK8 lub DNJXJ-7XBW8-2378T-X22TX-BKG7J

Wersję można pobrać ze stron Microsoft.