Working together to bring broadband to rural Veterans – Microsoft on the Issues

Our nation’s Veterans have contributed to our country in so many ways, in countless locations around the globe. When they return home, many Veterans who reside in rural areas are not able to access broadband internet which is critical to using telehealth services, gaining educational opportunities, and growing a small business or running a family farm.

There are 2.7 million Veterans enrolled in Veterans Affairs (VA) who are living in rural communities, 42% of them do not have internet access at home which could support their use of VA telehealth services, according to the U.S. Department of Veterans Affairs’, Veterans Health Administration’s Office of Rural Health. These rural Veterans live in areas where access to fast, reliable internet service may be limited or inaccessible and are facing higher rates of unemployment, longer drives to reach the nearest clinics and medical centers, and lower levels of educational attainment compared to their urban counterparts. Connectivity has the potential to improve this reality — with broadband, they can access telehealth services offered by the VA, identify and compete for well-paying jobs, improve and grow their own businesses, and take advantage of online education classes.

Microsoft and VA have been strategic partners, working together to improve the lives of Veterans, for more than 20 years. Today, I’m excited to share that Microsoft will begin expanding that work by helping VA to help bring connectivity to many Veterans living in rural towns and communities. Microsoft and its partners will be working with VA to provide capital, technology expertise, and training resources to bring broadband access to people in these underserved communities. Our hope is that this effort will unlock new economic opportunities, while also enhancing quality of life.

Through the partnership, we’ll help VA identify communities with Veterans in need and work with our internet service provider (ISP) partners across the nation to bring broadband services to those regions. Following our Airband Initiative model, we’ll also provide the Veterans in these newly connected communities with digital skills training so they can take advantage of the tools and services connectivity enables, including critical telehealth services provided by VA.

In the past 22 months, through the Microsoft Airband Initiative, we have seen firsthand just how many communities lack connectivity at broadband speeds and how this can hinder growth and new opportunities. We’ve also seen that partnering with ISPs to serve those most in need is an effective strategy to make progress quickly on this important issue. Our work with VA builds on those lessons and approach, which has resulted in partnerships that will bring connectivity to 1 million unserved rural residents in 16 states to date, with a plan to reach 3 million by 2022.

This also builds on our commitment to the military and Veteran community. We’re passionate about our work with this community and take a holistic approach to helping Veterans gain the critical career skills required for today’s digital economy through career training and re-training, soft-skills support, and hiring. The company’s cornerstone Veteran program, Microsoft Software & Systems Academy (MSSA), provides the Veteran community with an 18-week (or two nine-week terms) training for high-demand careers, with graduates gaining an interview for a full-time career at Microsoft or one of the company’s more than 400 hiring partners. We’re also proud of our strong network of partners, all of whom champion our same vision to assist the community.

We owe it to the men and women who have sacrificed so much for our nation. Veterans living in rural communities deserve to have the broadband internet access enjoyed by many who live in urban areas. Addressing the broadband gap across the country requires innovative solutions from both the public and private sectors, and we hope this partnership will help us make significant progress toward closing the connectivity gap for the Veteran community.

Tags: , , ,

Go to Original Article
Author: Microsoft News Center

Repp Health launches new patient tracking system

Repp Health has released Repp Eo — a real-time tracking ultra-wideband technology developed specifically for the healthcare market.

Similar to GPS, Repp Eo provides X and Y coordinates and uses a map interface with a blue dot. According to Repp Health, real-time location intelligence on patients, assets and staff can help hospitals guide more patients through the care process more efficiently.

“The crux of the issue is that, in the face of decreasing reimbursement, healthcare needs to accelerate the pace of care and deliver care more efficiently,” Repp Health Director of Business Development Heather Riley Swanson said. “In this age of Netflix, Uber and on demand, patients expect this of their healthcare providers as well.”

Repp Health claims that Repp Eo combines a limited on-premises footprint with secure, cloud-based data processing to create a high level of accuracy.

Repp Eo is similar to the real-time location system available from CenTrak, which is composed of various tags and badges, technology platforms, hardware infrastructure and other components. With CenTrak, the product typically includes location sensors that are attached to various assets, whether it be patients, staff members or pieces of equipment.

CenTrak claims that having tracking systems inside healthcare facilities helps reduce patient risks related to equipment errors, hospital-acquired infections or physical attacks by:

  • enabling staff to keep an eye on hygiene compliance;
  • creating contact tracing reports to know which staff members and patients have come into contact with an infected person/asset;
  • calling for help quickly in the event of an emergency;
  • identifying when machines or systems are due for maintenance;
  • letting staff know if a patient, particularly one with dementia or Alzheimer’s, has wandered into an area they shouldn’t; and
  • protecting infants from abduction attempts.

Go to Original Article
Author:

For Sale – Intel Skull Canyon – Core i7, 16gb, 512Gb Windows 10Pro

I built this intending to game and edit video, but I have an iPad and XPS13 and tbh this sits unused 99% of the time so time to sell on.

This is a great system that I used in conjuction with a TB3 Graphics card which offered great performance and flexibilty for its size.

System comes fully populated and with Windows 10 Pro license installed and activated, as can be seen in the images (I’ll unlink the key from my ID before shipping)

Basic Spec
Core i7 –6770HQ Quad Core with HT
16gb Kingston DDR4
512Gb – NVME Sandisk SSD
1 x HDMI, 1 x DP, 1 x Optical out
1 x Thunderbolt 3, 4 x USB 3, 1 x SD Reader
1xGbE
Windows 10 Pro License (Currently Running 1809)

Full Spec can be found

HERE . AnandTech Review can be found HERE

Price and currency: £450
Delivery: Delivery cost is not included
Payment method: PPG or Bacs
Location: Basingstoke
Advertised elsewhere?: Advertised elsewhere
Prefer goods collected?: I have no preference

______________________________________________________
This message is automatically inserted in all classifieds forum threads.
By replying to this thread you agree to abide by the trading rules detailed here.
Please be advised, all buyers and sellers should satisfy themselves that the other party is genuine by providing the following via private conversation to each other after negotiations are complete and prior to dispatching goods and making payment:

  • Landline telephone number. Make a call to check out the area code and number are correct, too
  • Name and address including postcode
  • Valid e-mail address

DO NOT proceed with a deal until you are completely satisfied with all details being correct. It’s in your best interest to check out these details yourself.

Go to Original Article
Author:

How to Request SSL Certificates from a Windows Certificate Server

In an earlier article, I showed you how to build a fully-functional two-tier PKI environment. At the end of that piece, I left you with the most basic deployment. In a second article, I showed you how to set up certificate templates. I will use this article to show you how to perform the most common day-to-day operations: requesting certificates from a Windows Certification Authority.

I used “SSL” in the title because most people associate that label with certificates. For the rest of the article, I will use the more apt “PKI” label.

The PKI Certificate Request and Issuance Process

Fundamentally, the process of requesting and issuing PKI certificates does not depend on any particular vendor technology. It follows this pattern:

  1. A public and private key is generated to represent the identity.
  2. “Certificate Signing Request” (CSR) is generated using the public key and some information about the identity.
  3. The certification authority uses information from the CSR, its own public key, authorization information, and a “signature” generated by its private key to issue a certificate.

The PKI Certificate Request and Issuance Process

The particulars of these steps vary among implementations. You might have some experience generating CSRs to send to third-party signers. You might also have some experience using web or MMC interfaces. All the real magic happens during the signing process, though. Implementations also vary on that, but they all create essentially the same final product.

I want you to focus on the issuance portion. You do not need to know in-depth details unless you intend to become a security expert. However, you do need to understand that certificate issuance always follows a process. Sometimes, an issuer might automate that process. You may have encountered that when signing up for a standard commercial web certificate. Let’s Encrypt provides a high degree of automation. At the other end, “Extended Validation” certificates usually require a higher level of interaction. At the most extreme, one commercial issuer used to require face-to-face contact before issuing a certificate. Regardless of the degree, every authority defines and follows a process that determines whether or not it will issue.

In your own environment, you can utilize varying levels of automation. More automation means more convenience, but also greater chances for abuse. Less automation requires greater user and administrative effort but might increase security. I lean toward more automation, myself, but will help you to find your own suitable solutions.

Auto-Enroll Method

I am a devoted fan of auto-enrollment for certificates. You only need to set up a basic group policy object, tie it to the right places, and everything takes care of itself.

If you recall from the previous article on certificate templates, you control who has the ability to auto-enroll a certificate by setting security on the template. You use group policy to set the scope of who will attempt to enroll the certificate.

Auto-Enroll Method - SSL Certificates

In the above graphic, the template’s policy allows all members of the default security group named “Domain Computers” to auto-enroll. Only the example “Certified Computers” OU links a group policy that allows auto-enrollment. Therefore, only members of the Certified Computers OU will receive the certificate. However, if Auto-Enroll is ever enabled for any other OU that contains members of the “Domain Computers” group, those members will receive certificates as well.

In summary, in order for auto-enroll to work, an object must:

  • Have the Autoenroll security permission on the certificate template
  • Fall within the scope of a group policy that enables it to auto-enroll certificates

You saw how to set certificate template security permissions in the previous article. We’ll go to the auto-enrollment policies next.

Auto-Enrollment Group Policies

The necessary policies exist at Computer or User ConfigurationPoliciesWindows SettingsSecurity SettingsPublic Key Policies. I am concerned with two policies: Certificate Services Client – Auto-Enrollment Settings and Certificate Services Client – Certificate Enrollment Policy.

First, Certificate Services Client – Auto-Enrollment Settings. To get going, you only need to set Configuration Model to Enabled. The default enrollment policy uses Windows Authentication to pull certificate information from Active Directory. If you’ve followed my directions, then you have an Active-Directory-integrated certification authority and this will all simply work. You will need to perform additional configuration if you need other enrollment options (such as requesting certificates from non-domain accounts).

certificate services client enrollment

Second, Certificate Services Client – Certificate Enrollment Policy. You only need to set Configuration Model to Enabled. Choose other options as desired.

auto-enroll

I think the first option explains itself. The second, Update certificates that use certificate templates, allow the certificate bearer to automatically request a replacement certificate when the certificate has updates. I showed you how to do that in the previous article.

Auto-Enrollment Security Implications

In general, you should not have many concerns with automatic certificate issuance. As followed so far, my directions keep everything under Active Directory’s control. However, you can enable auto-enrollment using other techniques, such as simple user/password verification via a URI. Anyone with local administrative powers can set local policies. Certificate templates can allow the requester to specify certificate subject names. Furthermore, some systems, like network access controls, sometimes simply require a particular certificate.

Think through who can request a certificate and who will accept them when configuring auto-enrollment scopes.

MMC Enrollment Procedure

MMC enrollment provides a great deal of flexibility. You can request certificates for you, your computer, or another entity entirely. It works on every single version of Windows and Windows Server in support, as long as they have a GUI. Since you can connect the console to another computer, you can overcome the need for a GUI. The procedure takes some effort to explain, but don’t let that deter. Once you have the hang of it, you can get through the process quickly.

First, you need to access the necessary console.

Accessing Certificate MMCs on Recent Windows Versions

On Windows 10 or Windows Server 2016+, just open up the Start menu and start typing “certificate”. At some point, Cortana will figure out what you want and show you these options:

encryption certificates

These options will work only for the local computer and the current user. If you want to target another computer, you can follow the upcoming steps.

Note: If you will use the console to request a certificate on behalf of another entity, it does not matter which console you start. The certificate template must allow exporting the private key for this mode to have any real use.

Accessing Specific Certificate MMCs Directly

On any version of Windows, you can quickly access the local computer and user certificates by calling their console snap-ins. You can begin from the Start menu, a Run dialog, or a command prompt. For the local computer, you must run the console using elevated credentials. Just enter the desired snap-in name and press Enter:

  • certlm.msc: Local machine certificates
  • certmgr.msc: Current user certificates

Note: If you will use the console to request a certificate on behalf of another entity, it does not matter which console you start. The certificate template must allow exporting the private key for this mode to have any real use.

Manually Add Specific Certificate Targets in MMC

You can manually add the necessary snap-in(s) from an empty MMC console.

  1. From the Start menu, any Run dialog, or a command prompt (elevated, if you need to use a different account to access the desired target), run mmc.exe.
  2. From the File menu, select Add/Remove Snap-in…
    console root
  3. Highlight Certificates and click Add:
    add or remove snap-ins
  4. Choose the object type to certify. In this context, My user account means the account currently running MMC. If you pick My user account, the wizard finishes here.
    certificates snap-in
  5. If you picked Service account or Computer account in step 4, the wizard switches to the computer selection screen. If you choose any computer other than local, you will view that computer’s certificate stores and changes will save to those stores. If you choose Computer account, the wizard finishes here.
    snap-in local computer
  6. If you selected Service account in step 4, you will now have a list of service accounts to choose from.
  7. If you want, you can repeat the above steps to connect one console to multiple targets:
  8. Once you have the target(s) that you like, click OK on the Add or Remove Snap-ins window. You will return to the console and your target(s) will appear in the left pane’s tree view.

Using the Certificates MMC Snap-In to Request Certificates

Regardless of how you got here, certificate requests all work the same way. We operate in the Personal branch, which translates to the My store in other tools.

Requesting a Certificate Using Template Defaults

You can quickly enroll a certificate template with template defaults. This is essentially the manual corollary to auto-enroll. You could use this method to perform enrollment on behalf of another entity, provided that you the template allows you to override the subject name. For that, you must have selected a console that matches the basic certificate type (a user console can only request user certificates and a computer console can only request computer certificates). You must also use an account with Enroll permissions on the desired template. I recommend that you only use this method to request certificates for the local computer or your current user. Skip to the next section for a better way to request certificates for another entity.

To request a certificate using a template’s defaults:

  1. Right-click Certificates and click Request New Certificate.
  2. The first screen is informational. The next screen asks you for a certificate enrollment policy. Thus far, we only have the default policy. You would use the Configured by you policy if you needed to connect without Active Directory. Click Next.
    certificate enrollment policy
  3. You will see certificate templates that you have Enroll permissions for and that match the scope of the console. In this screenshot, I used a computer selection, so it has computer certificates. If you expand Details, it will show some of the current options set in the certificate. If you click Properties, you can access property sheets to control various aspects of the certificate. I will go over some of those options in the next section. Remember that the certificate template to manually supply subject name information or it will ignore any such settings in your requests. Click Enroll when you are ready. The certificate will appear in the list.
    request certificates

Once you have a certificate in your list, double-click it or right-click it and click Open. Verify that the certificate looks as expected. If you requested the certificate for another entity, you will find the Export wizard on the certificate’s All Tasks context menu.

Creating an Advanced Certificate Request

You can use MMC to create an advanced certificate request. Most importantly, this process works offline by creating a standard certificate signing request file (CSR). Since it does not check your permissions in real time, you have much greater flexibility. I recommend that you use this method when requesting certificates on behalf of another entity. Follow these steps:

  1. Right-click Certificates, go to All Tasks, then Advanced Operations, and click Create Custom Request.
  2. The first screen is informational only. Click Next. On the next screen, choose your enrollment policy. If you’ve followed my guide, you only have two (real) choices: the default Active Directory policy or a completely custom policy. You could also choose to create a new local policy, which I will not cover. If you pick the Active Directory policy, it will allow you to pick from all of its known templates, which you can customize if needed. If you choose to Proceed without enrollment policy, you will start with an empty template and need to provide almost every detail. Make your selection and click Next.
  3. I took this screenshot after choosing the Active Directory enrollment policy. I then selected one base template. You can see that you also have options for the CSR format to use. If you chose to proceed without a policy, your Template options are No template (CNG key) or No template (Legacy key). CNG (Certificate Next Generation) creates v3 certificates while the Legacy option generates v2 certificates. Practically, they mostly deal with how the private key is stored and accessed. Common Microsoft apps (like IIS) work with CNG. Legacy works with almost everything, so choose that if you need to guess.
    custom request certificate enrollment
  4. On the Certificate Information screen, you will either see the template name that you chose or Custom request if you did not select an enrollment policy. To the right of that, near the edge of the dialog, click the down-pointing triangle next to Details. If you selected a policy, that will show the defaults. If you did not, it will show empty information. Click the Properties button to access property sheets where you can specify certificate options. Look at the screenshot in step 3 in the previous section. I will show the details dialog in the next section. Click Next when you have completed this screen.
  5. Choose the output file name and format. Most CAs will work with either type. Most prefer the default of Base64.
  6. You can now process the request on your Certification Authority.

Configuring Advanced Certificate Options in a Request

As mentioned step 3 in the above directions on using MMC to request a default template and in step 4 of the advanced request, you can use the Properties button on the Details section to modify parts of the certificate request prior to submitting it to the CA. If you selected a template that requires you to supply information, you will see an additional link that opens this dialog. You should always take care to inspect such a certificate after issuance to ensure that the CA honored the changes.

I will not cover every single detail. We will look at a few common items.

  • General: These fields are cosmetic. They appear when you see the certificate in the list.
    certificate properties
  • Subject: This busy tab contains identity information about the certificate holder. If the template only allows Active Directory information, then the CA will not accept anything that you enter here. For each type on the left, you can add multiple values. Make certain that you Add items so that they move to the right panes! Some of the more important parts:
    • Subject Name group: The fields in this group appear all combine to describe the certificate holder.
      • Common name: The primary identity of the certificate. Use a fully-qualified domain name for a computer or a full name for a user. Modern browsers no longer accept the value in the common name for authentication. Other tools still expect it. Always provide a value for this field to ensure the completeness of the subject group.
      • Country, Locality, Organization, etc.: Public CAs often require several of these other identity fields.
    • Alternative Name group: The fields in this group appear in the “Subject Alternate Name” (SAN) section of a certification. Browsers and some other tools will match entries in the SAN fields with the URL or other access points
      • DNS: Use this field to designate fully-qualified and short names that clients might use to access the certificate holder. Since web browsers no longer use the common name, enter all names that the owner might present during communications, including what you entered as the common name. Only use short names with LAN-scoped certificates. For instance, I might have a certificate with a common name of “internalweb.sironic.life” and give it an alternative DNS entry of “internalweb”. For load-balanced servers in a farm, I might have multiple DNS entries like “webserver1.sironic.life”, “webserver2.sironic.life”, etc.
      • IP Address (v4 and v6): If clients will access the certified system by IP address, you might want to add those IPs in these fields.

  • Extensions: The extensions govern how the bearer can use the issued certificate. Especially take note of the Extended Key Usage options.
  • Private Key: You don’t have a huge amount of private key options. In particular, you may wish to make the private key exportable.

The wizard will contain your options in the certificate request. The CA may choose to issue the certificate without accepting all of them.

Deprecated Web Enrollment Method

Once upon a time, Microsoft built an ASP page to facilitate certificate requests. They have not updated it for quite some time, and as I understand it, have no plans to update it in the future. It does still work, though, with some effort. One thing to be aware of: it can only provide v2 (legacy) certificates. It was not updated to work with v3 (CNG). If a certificate template specifies the newer cryptography provider, web enrollment will not present it as an enrollable option. Certificates must use the Legacy Cryptographic Service Provider.

web server properties

First, you must issue it a certificate. It responds on 80 and 443, but some features behave oddly on a port 80 connection. Installation of the Web Enrollment role creates the web site and enables it for 443, but leaves it without a certificate.

Follow the steps in the previous article to set up a web server certificate (requires Server Authentication extended key usage). Once you finish that, use one of the MMC methods above to request a certificate for the site. Remember to use its FQDN and optionally its NetBIOS names as DNS fields on the Subject tab. Then, follow these steps to assign it to the certificate server’s web site:

  1. Open Internet Information Services (IIS) Manager on the system running the Web Enrollment service or on any system that can connect to it.
  2. Highlight the server in the left pane. In the right pane, under IIS, double-click Server Certificates.
    internet information services manager
  3. The newly-issued certificate should appear here. Highlight it and click Enable automatic rebind of renewed certificate in the right pane. If it does not appear here, verify that it appears in MMC and reload this page. If it still does not appear, then you made a mistake during the certificate request or issuance process.
  4. In the left pane, drill down from the server name to Sites, then Default Web Site. Right-click Default web site and click Edit Bindings. You can also find a Bindings link in the far right pane.
  5. Double-click the https line or highlight it and click Edit… at the right.
    site bindings
  6. Under SSL certificate, choose the newly-issued certificate. Click OK, then Close to return to IIS Manager.
  7. Drill down under Default web site and click on CertSrv. In the center pane, double-click Authentication.
  8. In the center pane, highlight Windows Authentication. It should already be Enabled. In the right pane, click Providers.
  9. NTLM should appear in the provider list. If it does not, use the drop-down to select it, then Add to put it in the list. Use the Up button to move NTLM to the top of the list. Ensure that your dialog looks like the following screenshot, then click OK.
    providers

You can now access the site via https://yourcertserver.domain.tld/certsrv. You will need to supply valid credentials. It will display the start screen, where you can begin your journey.

Because of the v2 certificate limitation, I neither use nor recommend this site for certificate requests. However, it does provide a convenient access point for your domain’s certificate chain and CRL.

Alternative Request Methods

The methods that I displayed above are the easiest and most universally-applicable ways to request certificates. However, anything that generates a CSR may suffice. Some tools have interfaces that can communicate directly with your certificate server. Some examples:

  • certreq.exe: Microsoft provides a built-in command-line based tool for requesting certificates. You can use it to automate bulk requests without involving auto-enroll. Read up on its usage on docs.microsoft.com.
  • IIS Manager
  • Exchange Management Console

Other tools exist.

What’s Next

At this point, you can create PKI certificate templates and request them. With an Active Directory-integrated certificate system, all should work easily for you. However, if you were following the directions for the custom request, you ended up with a CSR. Passing a CSR to the certification authority requires different tools. In the next article, I will show how to perform routine operations from the Certification Authority side, such as accepting CSRs and revoking certificates.

Go to Original Article
Author: Eric Siron

Google Glass Enterprise Edition 2 resurrects AR for Google

Nearly six years after the release of its first augmented reality headset, Google has unveiled Google Glass Enterprise Edition 2, a wearable Google first pitched two years ago. The AR smart glasses aimed at businesses promises to improve on its predecessor in performance, camera, compatibility and style.

The first notable spec of Google’s Glass Enterprise Edition 2 is that it’s built on the Qualcomm Snapdragon XR1 platform. Featuring a four-core CPU and a new artificial intelligence engine, the 1.7 GHz chip based on 10nm architecture saves on power, while increasing performance, according to Google.

Google has also added a USB-C port intended to support faster charging and overall increased battery life; the headset lasts eight hours between charges. Glass 2 also features Bluetooth 5 and Wi-Fi 5 support.

The camera quality was bumped from 5 MP to 8 MP in Glass 2, yet with the same display specs — 640 x 360 pixels — as the first Glass model.

The new edition of Google’s augmented reality headset is also easier to develop for, according to Google. Glass Enterprise Edition 2 is built on Android Oreo, making it easy for users to integrate services and APIs they already use. Glass 2 now also supports Android Enterprise Mobile Management, so users can manage their headsets remotely, particularly useful for disabling the device if it gets lost or stolen.

And, the most noticeable change to Glass 2 is its appearance; Google now offers the AR headset in a thick, black “safety frame” — developed with Smith Optics — that appears more conventional than the original thin, wire-rimmed frames, and house most of its hardware in the right stem of the glasses. Google still offers a style similar to the original — a thin, wire frame that appears rimless.

Google Glass Enterprise Edition 2 is Google's newest augmented reality headset.
The Google Glass Enterprise Edition 2 is a wearable computer headset featuring safety frames by Smith Optics.

The first edition of Google Glass released in 2013 was intended to eventually be available to consumer-level users. However, the $1,500 price tag and slew of complications prohibited the product from reaching that level, and it was discontinued in 2015. In 2017, Google teased its eventual resurrection of Glass.

Glass 2 is explicitly aimed at businesses — particularly medical, manufacturing and logistics fields — and comes with a more accessible $999 MSRP. However, the product is only available through third-party partners, and pricing can vary depending on partners’ installment plans or supplementary services.

In February, Microsoft unveiled HoloLens 2, a headset that displays information across a user’s entire field of vision, unlike the Glass 2, which only projects in front of one eye. While the HoloLens 2 is more powerful than the Glass 2, it is significantly bulkier and starts at $3,500; the HoloLens 2 is also used by manufacturing businesses, as well as the U.S. military.

Lenovo also recently announced wearable AR technology, the Lenovo ThinkReality A6, also aimed at enterprise-level workers. The A6 is not yet generally available and the vendor has not released pricing information.

Go to Original Article
Author:

For Sale – Intel Skull Canyon – Core i7, 16gb, 512Gb Windows 10Pro

I built this intending to game and edit video, but I have an iPad and XPS13 and tbh this sits unused 99% of the time so time to sell on.

This is a great system that I used in conjuction with a TB3 Graphics card which offered great performance and flexibilty for its size.

System comes fully populated and with Windows 10 Pro license installed and activated, as can be seen in the images (I’ll unlink the key from my ID before shipping)

Basic Spec
Core i7 –6770HQ Quad Core with HT
16gb Kingston DDR4
512Gb – NVME Sandisk SSD
1 x HDMI, 1 x DP, 1 x Optical out
1 x Thunderbolt 3, 4 x USB 3, 1 x SD Reader
1xGbE
Windows 10 Pro License (Currently Running 1809)

Full Spec can be found

HERE . AnandTech Review can be found HERE

Price and currency: £450
Delivery: Delivery cost is not included
Payment method: PPG or Bacs
Location: Basingstoke
Advertised elsewhere?: Advertised elsewhere
Prefer goods collected?: I have no preference

______________________________________________________
This message is automatically inserted in all classifieds forum threads.
By replying to this thread you agree to abide by the trading rules detailed here.
Please be advised, all buyers and sellers should satisfy themselves that the other party is genuine by providing the following via private conversation to each other after negotiations are complete and prior to dispatching goods and making payment:

  • Landline telephone number. Make a call to check out the area code and number are correct, too
  • Name and address including postcode
  • Valid e-mail address

DO NOT proceed with a deal until you are completely satisfied with all details being correct. It’s in your best interest to check out these details yourself.

Go to Original Article
Author: