<div>
In the event that a computer (laptop) goes off site. What does this solution do while disconnected? Does it just queue them and bring them online the next time the device is on the network?
</div>


<div>
We are using this easy script:<br />
<a href="https://gallery.technet.microsoft.com/scriptcenter/Export-event-logs-from-09a1a90c" rel="ugc nofollow">https://gallery.technet.microsoft.com/scriptcenter/Export-event-logs-from-09a1a90c</a>
</div>


<div>
<b>&quot;In the event that a computer (laptop) goes off site. What does this solution do while disconnected? Does it just queue them and bring them online the next time the device is on the network? &quot;</b><br />
No you will not get Events from clients that are offline
</div>


<div>
Actually, event collectors are designed to allow mobile computers to disconnect and reconnect without losing logs. See my second link.
</div>


<div>
Second Jeremy with event collectors.
</div>


<div>
Jeremy provided a wonderful answer to the question asked. The solution is superior to the wanted process originally described as well.
</div>


<div>
<div class="content wysiwyg-content">
I have found a lot of suggestions for experting system logs using vbs but i prefer to use Powershell if possible.<br />
<br />
<b> Here is my situation</b><br />
<br />
We are wanting to export <b>ALL</b> event logs for ALL of our environments machines (mixture of Server 2012R2 and WIndows 8.1) to a storage device (network share) at a set interval. We will be migrating to Windows 10 so a general method that would work across all current Windows Versions (Server 2008+ and Windows 7+) would be amazing.<br />
<br />
Any help would be greatly appreciated
</div>
</div>


I have found a lot of suggestions for experting system logs using vbs but i prefer to use Powershell if possible.

 Here is my situation

We are wanting to export ALL event logs for ALL of our environments machines (mixture of Server 2012R2 and WIndows 8.1) to a storage device (network share) at a set interval. We will be migrating to Windows 10 so a general method that would work across all current Windows Versions (Server 2008+ and Windows 7+) would be amazing.

Any help would be greatly appreciated

Export System Event Logs With Powershell

Windows 8 is a personal computer operating system developed by Microsoft as part of the Windows NT family of operating systems, with an emphasis on improving its user experience on tablets. In particular, these changes included a touch-optimized Windows shell based on Microsoft's "Metro" design language, the Start screen, a new platform for developing apps with an emphasis on touchscreen input, integration with online services, support for USB 3.0, Advanced Format hard drives, near field communications, and cloud computing. Additional security features were introduced, such as built-in antivirus software, integration with Microsoft SmartScreen phishing filtering service and support for UEFI Secure Boot on supported devices with UEFI firmware.

Windows 8

Windows PowerShell is a task automation and configuration management framework from Microsoft, consisting of a command-line shell and associated scripting language built on the .NET Framework. PowerShell provides full access to the Component Object Model (COM) and Windows Management Instrumentation (WMI), enabling administrators to perform administrative tasks on both local and remote Windows systems as well as WS-Management and Common Information Model (CIM) enabling management of remote Linux systems and network devices.

Powershell

A desktop computer is a personal computer designed for use at a single location due to its size and power requirements, usually by one person. The most common configuration has a case that houses the power supply, motherboard, disk storage (usually one or more hard disk drives and optical disc drives); a keyboard and mouse for input; and computer monitor and printer for output. The case may be oriented horizontally and placed atop a desk or vertically and placed underneath or beside a desk.

Desktops

Servers are computing devices that are similar to desktop computers in that they have the same basic components, but are significantly different in size, configuration and purpose. Servers are usually accessed over a network, and many run unattended, without a computer monitor, input device, audio hardware or USB interfaces. Many servers do not have a graphical user interface (GUI), and are configured and managed remotely. Servers typically include hardware redundancy such as dual power supplies, RAID disk systems, and ECC memory, along with extensive pre-boot memory testing and verification. Critical components might be hot swappable, and to guard against overheating, servers might have more powerful fans or use water cooling.