Windows cloning. Unsa inyo gamit?

[gintusnumbernine]

---

based sa akong mga na try, uu 2 ka drive, 1 kay ang source ang other kay ang destination.

Using Macrium:
Install Macrium Reflect sa Source Drive then ipa run nya from there i clone nimo ang imong source to your destination.
-ma apil ug copy ang Macrium, so mahug nga clone jud siya hahaha i think hasta pud ang mga partition nimo.

Para nako mas convenient ang EaseUS Partition Master.

Using EaseUS Partition Master:
Install EaseUS Partition Master sa Source Drive. Then igo ra nimo i run ang iyang "OS Migration" nga feature. After nimo ug set sa source/destination kay ipa restart then sa dili pa na mo boot sa OS mupakita dayon na siya sa progress sa pag migrate sa OS. Pero iya gibuhat kay dili ingon migrate jud as-in mawagtang ang OS sa Source Drive, naa lang gihapon didto na haha
After sa migration process good to go nana ang destination drive.

Ang ako nasabtan sa "transfer daun sa pikas comp" kay ang HDD. If sakto akong pag sabot, oo, balhin ra na nimo dayon. Ang akong style is ang HDD man mismo akong i taod sa source system (PC kung asa ang OS source).

Wala pa ko naka try anang hirens.

Ako lang suggestion kay:
1) Since company man jud ka nag work, papalit ug license sa Acronis.
2) Make an image for all OS-hardware setup (Windows version & Motherboard hardware, para dili mangaboang ang drivers)
3) Keep the images for easier reformat/wipe sa mga PC kay igo ra nimo i-'restore' ang image to a destination drive, including installed software, basta naa lang sa image.

mao nay buhaton sa akong workmate bsta need niya different operating systems nya 1 ra ka PC ang available, para dili na mag cge reformat-reinstall sa OS and other shiz

[karren_arthur]

@gintusnumbernine ga libog ghapon ko. haha. wa pa jd ko ka try gd. HAHA

[cobarde]

@karren_arthur sa torrent ra ko mag downloadan,

[gintusnumbernine]

@karren_arthur
testing-testingi lang sa hahaha
nya kana lang pud mga pwede ma testingan ha, tingali ma sikwate na inyo pc sa office hahaha

bsta in-ana ra na siya

Install to source drive -> migrate OS/clone to destination drive -> done!

[3rd_Party]

acronis og paragon

[defender_1611]

since companya man ka ga work pag network install nalang.....set-up lang ka ug mini server din after nimo ug set-up sa imong mini server you can capture the newly set-up pc through WDS or windows Deployment services. ingon ani akong gi buhat sa previous company nako....

[karren_arthur]

since companya man ka ga work pag network install nalang.....set-up lang ka ug mini server din after nimo ug set-up sa imong mini server you can capture the newly set-up pc through WDS or windows Deployment services. ingon ani akong gi buhat sa previous company nako....

i like this idea da. hehe. thanks. iwill read this further on other sites. thanks bro. hope i can contact you via msgs if u dont mind

[defender_1611]

kay sa mag clone clone paka nga perting hasola...maypa ang network install kay no need naka mag abli abli sa system unit.

[defender_1611]

i like this idea da. hehe. thanks. iwill read this further on other sites. thanks bro. hope i can contact you via msgs if u dont mind

sure wala blema na....always ra ko online....

by the way here are the requirements of the WDS (Windows Deployment Services):

1. Operating System --> WDS is included with Windows Server 2003 with Service Pack 2, Windows Server 2008, Windows Server 2008 R2 and Windows Server 2012.

2. Active Directory --> The WDS server must be a member of a domain or be a domain controller in the domain. The latter is not recommended in a non-small network.

Note: If the WDS server is not joined to a domain, the following event occurs when you want to add it for the first time in Windows Deployment Services console:







Note: The AD DS domain and forest versions are irrelevant; all domain and forest configurations support Windows Deployment Services.

3. DHCP Server --> The PXE clients must be able to get an IP address that allows them to communicate with the WDS server.

Note: The preferred method is to install WDS on a member server that is not running the DHCP Server role.

4. NTFS Volume --> The image store is where the boot and installation images will be located. this must be on an NTFS volume on the WDS server.

5. Credentials --> You must have local administrator rights to install WDS on the server. Enterprise Administrator rights in the Active Directory forest are required to authorize the WDS server as a DHCP server so it can respond to PXE clients. Domain users will be able to access WDS deployment services from a PXE client. Note that authorization for Windows Server 2008 R2 WDS servers is optional.

Note: You cannot deploy WDS on a computer running a Server Core edition of Windows Server 2008, 2008 R2 and Windows Server 2012.

hope you will remember this before you set-up the WDS.

[defender_1611]

requirements for Deployment Server and Transport Server (Standalone mode, no dependency on Active Directory) are:


1. NTFS volume. The server running Windows Deployment Services requires an NTFS file system volume for the image store.

2. DNS. You must have a working DNS server on the network before you can run Windows Deployment Services.

3. DHCP. You must have a working DHCP server with an active scope on the network because Windows Deployment Services uses PXE, which relies on DHCP for IP addressing.

4. Credentials. To install the role, you must be a member of the Local Administrators group on the server.

- - - Updated - - -
@karren_arthur: kani lang sa akong matampo sa pagka karon.....