Tampilkan postingan dengan label Windows Server 2003. Tampilkan semua postingan
Tampilkan postingan dengan label Windows Server 2003. Tampilkan semua postingan
0

Mengetahui Product Key dan Serial Windows

Mengetahui CD Key Windows XP, Vista, dan 7 dengan ProduKey v1.45 – Mungkin kita pernah menginstall suatu program seperti Microsoft Office (Microsoft Office 2003, Microsoft Office 2007), Windows (Termasuk Windows 7 dan Windows Vista), Exchange Server, dan SQL Server namun setelah program tersebut terpasang di komputer kita kehilangan CD Key atau Keygen. ProduKey dapat menolong kita dari masalah tersebut.
ProduKey adalah salah satu software freeware/gratis untuk menampilkan CD Key program yang telah terpasang di komputer. Prinsip kerja dan cara menggunakannya sangat mudah, cukup dengan menginstall produKey maka akan ditampilkan serial number/CD Key program yang telah terinstall di komputer kita.
Dengan cara ini, jika kita diberi software yang telah terinstall di komputer namun tidak mendapatkan CD Key-nya maka bisa menggunakan software ProduKey lalu bisa menuliskannya dalam bentuk hard copy agar tidak hilang kembali.

Serial Number program yang dapat diketahui ProduKey :
  • Microsoft Windows 98/ME
  • Microsoft Windows 2000
  • Microsoft Windows NT
  • Microsoft Windows XP
  • Microsoft Windows Vista
  • Microsoft Windows Server 2003
  • Microsoft Windows 7 (Works only for some of the Windows 7 versions, see the known problems section)
  • Microsoft Office 2000 (Only ProductID is displayed)
  • Microsoft Office 2003
  • Microsoft Office 2007
  • Microsoft Office 2010
  • Microsoft SQL Server 2000
  • Microsoft SQL Server 2005
  • Microsoft Exchange Server 2000
  • Microsoft Exchange Server 2003
System Requirements :
supported on Windows 2000/XP/2003/2008/Vista/7.

Source: carasetting
0

Membuat Installer Windows 7 dengan FD

Cara membuat installer windows 7 dengan Flashdisk (FD) USB. Cara tutorial ini akan menggunakan sebuah software gratis yaitu koala. software ini memungkinkan untuk membuat bootable Flashdisk USB thumb drive installer untuk Windows 7, Windows Vista dan Windows Server System 2008. Kalo untuk windows XP belum dicoba.

Cara Membuat Bootable Flashdisk USB Drive Installer untuk Windows 7
Koala membuat bootable USB dari CD Windows bukan file ISO. Maka untuk menciptakan sebuah installer bootable USB thumb drive, Sobat membutuhkan komputer yang menjalankan Windows (Windows XP atau yang lebih baru), DVD untuk OS Windows yang ingin dibuat USB bootable installer (Windows 7, Vista, Windows Server System 2008) , NET framework. 2.0 atau yang lebih tinggi dan USB flashdisk dengan kapasitas min. 4 GB.

Berikut caranya :
  1. Download Koala disini. 
  2. Masukkan DVD untuk Windows 7 (atau Vista atau Windows System 2008) ke dalam optical drive PC.
  3. Masukkan flashdisk (USB thumb disk atau pen disk) dengan kapasitas 4GB ke dalam drive USB PC.
  4. Jalankan program Koala.

Software Koala
  1. Click Scan pada bagian Source untuk melakukan scan source (optical drive) OS yang akan dijadikan installer bootable USB.
  2. Click Scan pada bagian Destination untuk melakukan scan drive USB yang akan dijadikan installer bootable.
  3. Click tombol Start untuk memulai proses pembuatan installer bootable USB untuk Windows.

+/- 10 menit, sebuah installer bootable USB thumb drive sudah siap untuk melakukan instalasi Windows 7 (atau Vista, windows Server System 2008)!!!

Source: sandydoank12
0

Terminal Server User Access Permissions

Yap X Liong Selasa, 14 Desember 2010 , ,
Ketika saya sudah melakukan install Terminal Server pada OS Windows Server 2003 X64 ternyata terdapat error "To log on to this remote computer, you must have Terminal Server User Access permissions on this computer. By default, members of the Remote Desktop Users group have these permissions. If you are no a member of the Remote Desktop Users group or another group that has these permissions, or if the Remote Desktop User group does not have these permissions, you must be granted these permissions manually." dengan gambar seperti dibawah ini :

Solusinya yaitu :

0

Error Firewall IPNat.sys

Yap X Liong Senin, 13 Desember 2010 , ,
Masalah ini terjadi ketika Server tidak bisa diakses oleh Computer lain, padahal melalui Server tersebut akses ke ip terdapat folder-folder yang disharing. Dan computer lain tidak bisa melakukan ping ke server.
Solusinya :
1. Klik kanan My Computer>Manager>Services and Applications>Services.
2. Disable Routing and Remote Access service
3. Setting ulang Gateway pada TCP/IP
4. Jika diperlukan lakukan "Repair"
5. Masuk CMD dan jalankan perintah "ipconfig /flushdns"
Beres deh.

Found this tidbit while researching this problem:
Can't enable windows Firewall on a RRAS server - Windows firewall cannot run because another program or service is running that might use the network address translation component (Ipnat.sys)
0

Windows Cannot Set The Password

Yap X Liong Jumat, 10 Desember 2010 , , ,
When you are adding users to a Windows Server 2003 you receive a message

Titled: Active Directory

And the stop message:
Windows cannot set the password for because: The password does not meet the password policy requirements. Check the minimum password length, password complexity and password history requirements.

http://www.tacktech.com



Your IT experience should have taught you a few things:
1: Computers need to be more secure.
2: Users don't want to deal with security.
(More specifically they don't want to enter in difficult passwords.)



By default Windows Server 2003 requires passwords to meet the following criteria for strong passwords.

  • Has at least 6 characters
  • Does not contain "Administrator" or "Admin"
  • Contains characters from three of the following categories:
    • Uppercase letters (A, B, C, and so on)
    • Lowercase letters (a, b, c, and so on)
    • Numbers (0, 1, 2, and so on)
    • Non-alphanumeric characters (#, &, ~, and so on)
Caution: Loosening password restrictions decreases security.



Select Domain Security Policy from Administrative Tools.



Click on Security Settings > Account Policies > Password Policy.

Right-click on Minimum password length in the right pane.
0

How to Crack Terminal Services

HOW TO RESET WINDOWS TERMINAL SERVICES 3 MONTH TRIAL
Warning: greyhat content.

Thanks to a Microsoft article, I've found out that it is very easy to extend your Windows Terminal Services 3-month trial or experience time. It's so easy that I'm sure many administrators have done this in their own systems, while waiting for their managers or financial staff to buy the definitive licenses (not being hypocrite here).

Following these instructions, you don't have to crack any program. You won't mess with your system. The magic is to only delete the licenses databases both in the server and the clients, and let windows re-create them for you.

----

Make sure you've installed "Terminal Services Licensing". By the way, this method only makes sense if you need to use Terminal Services in Application Mode, which is the one that requires licensing.

The idea is quite simple.

First, disconnect all users from the terminal. If you need to do this remotely, you can also disconnect yourself, and access the files remotely.
  1. Go to %WINDIR%\system32\lserver
0

Terminal Server User Access permissions

Sudden "...you must have Terminal Server User Access permissions on this computer." Error.

I have a Small Business Server 2003 R2 Server running Team Foundation Server tucked out of the way to conserve desk space (three servers, two clients, two desks: not much space).  I don't have it hooked up to a monitor (one: don't have that many monitors, and two: desk space).  So, I've been merrily using Remote Desktop Connection (RDC) in Windows XP to connect to this server to perform my various administration tasks (like install service packs, hot fixes, etc.).
Well, I finally had a couple of cycles to install some hotfixes for the new daylight savings time changes to various components, so I sparked up RDC to get the ball rolling on my server--as I have done many times before.  I was greeted with a message box as I logged in:
To log on to this remote computer, you must have Terminal Server User Access Permissions on this computer. By default, members of the Remote Desktop group have these permissions. If you are not a member of the Remote Desktop Users group or another group that has these permissions, or if the Remote Desktop User group does not have these permissions, you must be granted these permissions manually.
Needless to say I was dumbfounded--it worked fine yesterday.  After a bit of searching, it appears it was the 120 day anniversary of creating this server and Terminal Server (which is what is used for an application server in Small Business Server) had "expired" (i.e. its grace period for CALs had expired).  I was used to installing Windows Server and setting up Terminal Server for remote administration (there was a setting for that in Windows Server, I honestly don't remember what Small Business Server asked me when I installed; it certainly wasn't clear it was different the other Windows Server installation processes).  Apparently I missed the memo that remote administration is now called "Remote Desktop".  Clearly a WTF moment.
As it turns out, the hoops to get back to the ability of remote administration aren't clearly documented (I actually couldn't find any documentation on the process, I actually inferred the process from various non-Microsoft sources--there could be documentation somewhere, I just didn't find it).  The process requires that Terminal Server be uninstalled, the server rebooted, and Remote Desktop be re-enabled.  A point-list of the steps:
  1. Run Add/Remove Programs (run "appwiz.cpl")
  2. Click Add/Remove Windows Components (Alt-W)
  3. Uncheck Terminal Server
  4. Press Next>.
  5. Follow instructions, including rebooting.
  6. Open System control panel applet (run "sysdm.cpl")
  7. Click Remote tab.
  8. Check Enable Remote Desktop on this computer. (because removing Terminal Server disables this)
  9. Click Select Remote Users...
  10. Make sure administrators is in the list.
  11. Click OK.
  12. Click OK. for the next dialog.
  13. Wait a few minutes for things to get up and running and you're no ready for remote administration again.
I hope this helps someone get back up and running faster than I did...
 
Source: PeterRitchie
 
Copyright 2010 catatan si b4r12y
Flash Blue Blogger template by b4r12y