Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 hours ago.
Improve this question
My company is a Lenovo shop and we stood up a WDS server some time ago that boots computers into MDT to deploy images. We've done all sorts of models, from T480s to T490s, T14s, P51, P52, P53, without a single issue. I never did much with drivers in the boot image because it always just seemed to work. Until, that is, we got some new T14 generation 2 and P15 generation 2 models. No matter what I do, they will not successfully boot into MDT.
What happens is we PXE boot these new model machines, they contact the PDX server, load the boot image, I see the background image we set in MDT, and then we immediately get this image, or sometimes, it displays the prompt to start the deployment wizard, and THEN after clicking the start button it displays this error.
On the P15 gen2:
A connection to the deployment share (path) could not be made. The following networking device did not have a driver installed: PCI\VEN_8086&DEV_15F3&SUBSYS_22D817AA&REV_03.
On the T14 gen2:
A connection to the deployment share (path) could not be made. The following networking device did not have a driver installed: PCI\VEN_8086&DEV_15F3&SUBSYS_22D817AA&REV_20.
Once and only once, a T14gen2 went all the way through the deployment task sequence, booted into Windows 10, and THEN displayed the error.
Some googling led me to this page, where I found that the T14gen2 and P15gen2 have specific WinPE 10 driver packs: https://support.lenovo.com/us/en/solutions/ht074984-microsoft-system-center-configuration-manager-sccm-and-microsoft-deployment-toolkit-mdt-package-index
Ok, great. Problem solved. So I downloaded and extracted each package, created a folder in my Out-of-Box driver packs, imported the drivers into there, made a selection profile for that folder, and configured WinPE to grab drivers from there in the Deployment Share properties, then imported that boot image into WinPE.
Then I PXE booted each model and got the same behavior. I'm a little stuck, and wondering if anyone here has run into this before or has any clues on where to go.
Also, originally, I just left the WinPE drivers on 'All,' imported all of the P15g2 and T14g2 drivers into Out-of-Box drivers, and just let the boot image grab what it needed. That broke everything. Computers would boot from the image and then display a message saying that Windows couldn't boot because iaStorAfs.sys couldn't be found. I had to rebuild the entire MDT environment to recover from that.
So right now, just the WinPE drivers for the T14g2 and the P15g2 are being injected into the image, as well as the drivers for the USB-C gen2 dock (https://download.lenovo.com/km/media/attachment/USBCG2.zip). Every other Lenovo model still boots into MDT no problem, and the two models I loaded drivers for don't.
Any insight appreciated! This has been driving me nuts for a while.
I got the same error with Lenovo Thinkpad T14 Gen2(Type 20W0).
PCI\VEN_8086&DEV_15FC&SUBSYS_22C917AA&REV_20
How to reslove this issue, go to Lenovo website https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-t-series-laptops/thinkpad-t14-gen-2-type-20w0-20w1/downloads
and enter your serial number to download the network driver,my Thinkpad NIC was Intel i211-v, so I download it and import to MDT out-of-box WinPE driver,after that I boot my laptop via PXE and no error prompt,about 15 mins complete the Win10 deployment, hope this can resolve your problem.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
The Problem
Schwab only supports Windows and Mac for its StreetSmart Edge Cloud (SSEC), not Linux. However SSEC is Citrix based, which has a Linux implementation. Unfortunately, it does not work out of the box. How do I get it working on Linux?
Background
One of the most difficult type of software to find on Linux is investment trading software. For years, I had to maintain a Windows machine for this purpose alone.
One of the most sophisticated platform for this is Schwab SmartStreet Edge Cloud version. The only problem is that Schwab only supports Windows and Mac, not Linux. Of course there are other trading platforms, but few can be installed on Linux and I like StreetSmart best.
But isn't Mac a close cousin of Linux? Why can't we seem to get trading software to work on Linux, especially when it is a cloud version of the trading platform? After all, anything that you can do on a Win or Mac browser, you can do on a Linux browser.
So, my question is how can I install a trading platform with all the sophisticated charting and complex trading parameters, such as stop, limit and bracket orders?
Solution
Now, I am going to answer my own question with a solution.
Here is what worked for me. I have been using StreetSmart Edge for over 6 months on my Linux with this solution. Best of all, it does not rely on Wine or dual booting.
Step 1
Download the latest Citrix Workspace app for Linux Web client (x86_64) for 64 bit architecture or (x86) for 32 bit architecture or (ARM HF) for ARM processor machines. I have only tested on the (x86_64), so cannot speak for the others.
Go to the citrix.com and look for the workspace app download page.
Under Available Downloads, choose the type of package you need. I chose Debian Packages. You may need the RPM Packages. Choose the Web Packages (Web Workspace app only) download for your architecture.
On Debian, you are immediately offered a chance to install with GDebi. Click on OK to install.
On RedHat type distros, there are analogous steps.
Or simply install the downloaded file manually, using your OS normal installation procedure for downloaded packages. Be sure you use a method such as GDebi to install needed dependencies as well.
Everything should appear to install correctly without an error message, however, when you try to launch StreetSmart Edge Cloud, you will get the following error message:
SSL error
Contact your help desk with the following information: You have not chosen to trust "DigiCert Global Root G2", the issuer of the server's security certificate (SSL error 61).
Step 2
Create a soft symbolic link to DigiCert_Global_Root_G2.crt which should be in your mozilla ca-certificates.
In my case - Debian 9 - the command to create the symbolic link was as follows:
sudo ln -s /usr/share/ca-certificates/mozilla/DigiCert_Global_Root_G2.crt /opt/Citrix/ICAClient/keystore/cacerts/DigiCert_Global_Root_G2.pem
You may need to search for the mozilla directory to find the correct path for your setup. Also, you may need to search for the Citrix ... cacerts directory to find the correct path for your setup. Replace the ln -s syntax above with the one corrected for your paths.
Step 3
Reboot. I am not certain this is actually necessary, but it can't hurt.
Hurray! You should now be able to use Schwab StreetSmart Edge on your linux.
Now go out and make lots of money and donate it to charity. ... that includes supporting your favorite open source software!!
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I have maked a backup from my VMWare Virtual Machine. I have imported it into the source folder.
At the first time i can start the VM, it shows me the error, but i can start it. But when i reboot the VM, the error shows me, but the VM dont start.
shows to me and the VM dont start, error :
"piix4_smbus 0000:00:007.3" Host SmBus controller not enabled!"
I have tried to add into the blacklist.conf file this line : blacklist i2c-piix4
But it still dont works.
Have you tried changing the dash in blacklist i2c-piix4 to an underscore, like blacklist i2c_piix4? That may also solve the problem.
Well I wanted to post this on a ubuntu forum, but didn't have enough reputation, so I just post it here (same error on kali linux)
So this just happend to me and I wanted to share it with y'all, perhaps it helps somebody:
So I run Kali Linux in a VMware enviroment on Windows and I was away from my computer. It went
to sleep (while transfering files to a shared windows folder) and when I came back it only
showed a black screen. So I did a restart but then a blue screen happend. After restarting my
host I went and tried to power up the kali linux OS, then I got the following error:
Piix4_SMBus: 000:00:07.3: Host SMBus controller bus not enabled
not only that, it was stuck on a initramfs console. After trying all the stuff I found related
to this error (adding the blacklist stuff in any imagionable way) I went back to the error.
If you are in the initramfs console then type exit. It should show a error what is happening.
For me it showed that the /dev/sda1 had problems and I had to run fsck manually. What I did
not mention before is that I managed to get inside the kali linux OS by adding the original ISO
as a CD to VMware. I then entered the boot menu with F2 and changed the boot order to have CD on top.
You then get additional advanced boot options, also the recovery kali linux OS. (the graphical didn't work,
just use the console one) follow all the steps and enter the /dev/sda1 as root console. Then type the following
commands:
mount -o remount,ro /
fsck
it should do a fsck scan now and for me it showed a lot of errors. Just press enter on every error and then do
a reboot. Change the boot order in the BIOS again and then it should boot normally.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
Our customer has about 800+ computers running Windows XP distributed across the country. Each computer can be accessed using TeamViewer. The goal is to replace XP by a Linux distribution remotely.
Does anybody know if this is possible, and where to start?
Thanks!
PXE is your only realistic hope:
Some on-site assistance is needed to press F12 at Bios before Windows XP boot:
A) On PC-A, setup DHCP server that refer DHCP-client to PXE server that download Linux ISO from a web server (of course all three can be a Windows machine in the same LAN segment onsite)
B) reboot PC-B onsite to reboot machine and press F10-F12 to choose Boot-options
C) then choose network-boot (PXE-Boot)
further reading : https://www.vercot.com/~serva/
guide: https://youtu.be/nnxgFpUr1Og?t=39
Note: Make sure you have enabled proxyDHCP and not DHCP Server
I would try with something like these:
Clonezilla, which works by replicating a previously prepared disk image to one or more computers booted inside a network segment
Cobbler, which works like a provisioning server for Linux based machines
Of those options, I have used Clonezilla with success. As long as the prepared base image doesn't change too frequently, the main time consuming tasks would be related with configuring the Clonezilla server and building that seed image.
I did a basic test of Cobbler and it worked fine in my environment, being this a way that would be more apt to deal with requirement changes.
Please also note that both options require some network configuration, like DHCP server settings that work with the PXE protocol.
Also, for your requirement, someone, a human being, would be needed to execute one or more of these tasks:
Properly enable network booting in the BIOS of each of the 800+ machines, unless it has already be done before
Boot the machines to install the new operating system
The network booting option, based on the PXE specification, should be supported by the motherboard of those machines and have higher booting priority than other devices, like CD drives, hard drives, etc.
Another thing to consider for the couple of options I'm suggesting, is how are those 800+ distributed across the country. The more disperse they are, the more cumbersome this task will be. Quite contrary, if there are few places were those machines are located, the more feasible this task will be; for example, by preparing and testing a server, computer or laptop that you then carry to each of those few places and installing the new operating system.
Regarding the option to boot using the public Internet to reach a remote deployment server, I don't know about how that could be done; in fact, for me that would be something quite interesting to learn about. If something like this is possible, another variable to note is the hardware compatibility of the destination machines, because as far as I know, protocols like PXE do some kind of multicast or broadcast in the local network segment and I presume those 800+ machines don't have recent motherboards with advanced firmware that could support more modern boot protocols.
That's all for now.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 7 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
I use windows 8.1 64-bit on my machine and recently, without having installed any new application, I get the following error when connecting to VPN:
Error 720: Unable to establish a connection to the remote computer.
Might need to change the network settings for this connection.
Tenentei already follow several tutorials but in no've succeeded.
Example configuration that tried to accomplish:
http://en.remontka.pro/error-720-windows-8-and-8-1-solved/
Thankyou
Since I can't find a complete or clear answer on this issue, and since it's the second time that I use this post to fix my problems, I post my solution:
why 720? 720 is the error code for connection attempt fail, because your computer and the remote computer could not agree on PPP control protocol, I don't know exactly why it happens, but I think that is all about registry permission for installers and multiple miniport driver install made by vpn installers that are not properly programmed for win 8.1.
Solution:
check write permissions on registers
a. download a Process Monitor
http://technet.microsoft.com/en-us//sysinternals/bb896645.aspx and run it
b. Use registry as target and set the filters to check witch registers aren't writable for netsh: "Process Name is 'netsh.exe'" and "result is 'ACCESS DENIED'", then get a command prompt with admin permissions and type netsh int ipv4 reset reset.log
c. for each registry key logged by the process monitor as not accessible, go to registers using regedit anche change these permissions to "complete access"
d. run the following command netsh int ipv6 reset reset.log and repeat step c)
unistall all not-working miniports
a. go to device managers (windows+x -> device manager)
b. for each not-working miniport (the ones with yellow mark): update driver -> show non-compatible driver -> select another driver (eg. generic broadband adapter)
c. unistall these not working devices
d. reboot your computer
e. Repeat steps a) - d) until you will not see any yellow mark on miniports
delete your vpn connection and create a new one.
that worked for me (2 times, one after my first vpn connection on win 8.1, then when I reinstalled a cisco client and tried to use windows vpn again)
references:
http://en.remontka.pro/error-720-windows-8-and-8-1-solved/
https://forums.lenovo.com/t5/Windows-8-and-8-1/SOLVED-WAN-Miniport-2-yellow-exclamation-mark-in-Device-Manager/td-p/1051981
This solved my 720 problem. The idea is to change the driver of the faulty WAN to another network adaptar driver, and then we are able to uninstall the WAN device and then reboot the system.
https://forums.lenovo.com/t5/Windows-8-and-8-1/SOLVED-WAN-Miniport-2-yellow-exclamation-mark-in-Device-Manager/td-p/1051981
First I would like to thank Rose who was willing to help us, but your answer could solve the problem on a computer, but in others there was what was done could not always connect gets error 720.
After much searching and contact the Microsoft support we can solve.
In Device Manager, on the View menu, select to show hidden devices.
Made it look for a remote Miniport IP or network monitor that is with warning of problems with the driver icon. In its properties in the details tab check the Key property of the driver.
Look for this key in Regedit on Local Machine, make a backup of that key and delete it. Restart your windows.
Reopen your device manager and select the miniport that had deleted the record. Activate the option to update the driver and look for the option driver on the computer manually and then use the option to locate the driver from the list available on the computer on the next screen uncheck show compatible hardware. Then you must select the Microsoft Vendor and the driver WAN Miniport the type that is changing, IP or IPV6 L2TP Network Monitor.
After upgrading restart the computer.
I know it's a bit laborious but that was the only way that worked on all computers.
Based on the Microsoft support KBs, this can occur if TCP/IP is damaged or is not bound to your dial-up adapter.You can try reinstalling or resetting TCP/IP as follows:
Reset TCP/IP to Original Configuration- Using the NetShell utility,
type this command (in CommandLine): netsh int ip reset [file_name.txt],
[file_name.txt] is the name of the file where the actions taken by
NetShell are record, for example netsh hint ip reset fixtcpip.txt.
Remove and re-install NIC – Open Controller and select System. Click
Hardware tab and select devices. Double-click on Network Adapter and
right-click on the NIC, select Uninstall. Restart the computer and
the Windows should auto detect the NIC and re-install it.
Upgrade the NIC driver – You may download the latest NIC driver and
upgrade the driver.
Hope it could help.
I had the same problem. Most posted solutions would not work.
I ran sfc /scannow and it reported that some errors could not be fixed.
To address that problem I ran the command
Dism /Online /Cleanup-Image /RestoreHealth
Ironically, I later found the WAN errors had gone away, the 720 VPN error went away and my VPN worked.
Hard to believe that the WAN errors were corrected by this rather esoteric command, but it's worth a try.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I am wanting to install OpenShift Origin on my PC running Windows 7.
I am completely new to Linux environments and terminology but wanted to 'look around' the OpenShift product with the hope that I can become familiar with its offerings and features.
So I have started here:
https://www.openshift.com/products/origin
Where the instructions are:
"The easiest way to run OpenShift Origin locally is to download an image suitable for running on a VM. The image will work on KVM , VirtualBox or VMWare . You can also spin up a VirtualBox instance using Vagrant or build your own machine using Puppet".
I have downloaded openshift-origin.latest.tgz and I am assuming the next step is to download and install a 'VM' (something I also have never used)?
I have heard the name VMWare before but when I visit the site there seem to be 15+ different products and I'm not sure which one is required for the above task.
So, is it possible for someone to provide a <ul> of steps required to install and run OpenShift Origin on Windows 7?
A google search for how to install openshift origin on windows 7? does not seem to return any immediately obvious results (the first result links to an article that starts with [obsolete]).
There is a video called 'open shift origin setup' here:
http://youtu.be/rzW3N_C5sIE
But it starts with a file called 'openshift_origin.iso' and not the 'openshift-origin.latest.tgz' that I have downloaded and then it gets into some terminal coding that is completely foreign to me.
Any pointers appreciated.
Edit:
In addition to accepted answer below, as virtual machines may be a bit ominous to newbies here are some screenshots which show the installation of VirtualBox, it was really pretty easy.
For Windows 7, I downloaded VirtualBox 4.2.16 for Windows hosts x86/amd64 from:
https://www.virtualbox.org/wiki/Downloads
and then ran the installer:
Then you will see a few of these type of screens, just click 'Install'.
Unfortunately then when running OpenShift, as per instructions in accepted answer, I got this message:
And I haven't been able to find a workaround to this yet.
But this error shouldn't occur for those who have hardware acceleration enabled.
VirtualBox
VirtualBox is freely available.
Open VirtualBox from the Start Menu - this opens the VirtualBox Manager.
Open the menu File > Import Appliance or press CTRL+I.
Click Open Appliance...
Browse to the folder you downloaded OpenShift Origin to.
Select the .ovf file.
Press Next.
Press Import.
It'll import the file for a while (roughly 2 minutes on my computer) and show up as a Virtual Machine afterwards. You can just click Start and it'll boot up.
VMWare
VMWare Player is free for personal non-commercial use while most other VMWare products are not.
I haven't personally tried this route, but it seems easy enough to just open the .vmx file directly.
Your choices of software to run the ISO (VM image with Fedora) on Windows is VirtualBox or VMWware Workstation. Here's an interesting article that compares the 2:
http://www.infoworld.com/d/virtualization/review-vmware-workstation-9-vs-virtualbox-42-203277
2 unrelated things here...
First, if you do not have a hardware virtualization enabled 64 bit processor (listed as VT-X on Intel chips, and AMD-V on AMD processors), then you cannot host an OpenShift Origin VM, which itself spawns VMs, and thus not only needs the virtualization enabled processor, but needs its VirtualBox VM enabled for virtualization (a checkbox under System/Acceleration in the settings for the VM).
Second, OpenShift Origin relies on multicast DNS, which is not supported on Windows 7, so it won't work.
If you can install Fedora 20 Alpha (I expect Fedora 19 will work, but I haven;t tried it) onto metal, then install VirtualBox and the nss-mdns RPM, that should work.
Been there, done that, got the headache.