Die Suche ergab 163 Treffer

von loggenk
06 Feb 2017, 10:05
Forum: Free support
Thema: Package not visible in Configed (SOLVED)
Antworten: 6
Zugriffe: 4465

Re: Package not visible in Configed

Hi Rupert,

When i use package manager i receive message that product is succelfully installed. Package is uploaded to repository.

Just created a new package, same behavior.
Till last week everything was fine

Greetings,

Kees...
von loggenk
03 Feb 2017, 12:05
Forum: Free support
Thema: Package not visible in Configed (SOLVED)
Antworten: 6
Zugriffe: 4465

Re: Package not visible in Configed

Yes, multiple times.
Restarted all servers.
Checked in package one server at the time.
Package is in repository.
von loggenk
03 Feb 2017, 08:13
Forum: Free support
Thema: Package not visible in Configed (SOLVED)
Antworten: 6
Zugriffe: 4465

Package not visible in Configed (SOLVED)

Hi, I created a package in opsi. Tried to install the package to config server and depots. When its done the package is not visible in configed. Command I use is : "opsi-package-manager -i -d ALL packagename and version.opsi I created package after opsi-setup --set-rights. After creating again ...
von loggenk
19 Jan 2017, 08:26
Forum: Free support
Thema: No PXE boot since Win10 4.0.7.1-2 (SOLVED)
Antworten: 12
Zugriffe: 7900

Re: No PXE boot since Win10 4.0.7.1-2

Hi Niko, Thanks for your answer. I'm aware of that. Problem seems to be that clients on depots starts miniroot.bz2 for a very short moment. After that i receive a window asking me if i want to run from local disk, x86 or x64. After that entry for system in tftpboot is gone. So it seems to me that it...
von loggenk
18 Jan 2017, 09:10
Forum: Free support
Thema: No PXE boot since Win10 4.0.7.1-2 (SOLVED)
Antworten: 12
Zugriffe: 7900

Re: No PXE boot since Win10 4.0.7.1-2

Hi, I restored a backup. But now i have another problem. When i try to image from a depot Opsi doesn't see the waiting image. In tftpboot/pxelinux the entry is present in the config server. root@opsi-nl-dev:~# cat /tftpboot/linux/pxelinux.cfg/01-00-50-56-9b-d7-48 default opsi-install label opsi-inst...
von loggenk
17 Jan 2017, 15:30
Forum: Free support
Thema: No PXE boot since Win10 4.0.7.1-2 (SOLVED)
Antworten: 12
Zugriffe: 7900

Re: No PXE boot since Win10 4.0.7.1-2

I'm a bit further now. But just a bit!

It does see the image now. But now it can't load pxelinux.cfg/01-d4-81-d7-5a-eb-d5
von loggenk
17 Jan 2017, 10:28
Forum: Free support
Thema: No PXE boot since Win10 4.0.7.1-2 (SOLVED)
Antworten: 12
Zugriffe: 7900

Re: No PXE boot since Win10 4.0.7.1-2

This happens when i try to image a win7-x64: Jan 17 10:25:15 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.cfg/C0A80B3 to 192.168.11.54:57092 Jan 17 10:25:15 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.cfg/C0A80B to 192.168.11.54:57093 Jan 17 10:25:15 opsi-nl-dev atftpd[2871]: Serving linux/...
von loggenk
17 Jan 2017, 10:25
Forum: Free support
Thema: No PXE boot since Win10 4.0.7.1-2 (SOLVED)
Antworten: 12
Zugriffe: 7900

Re: No PXE boot since Win10 4.0.7.1-2

Thnxs Mathias, I don't know what problem is. But this seems not ok. Jan 17 10:21:31 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.0 to 192.168.11.54:2070 Jan 17 10:21:31 opsi-nl-dev atftpd[2871]: Serving linux/pxelinux.0 to 192.168.11.54:2071 Jan 17 10:21:31 opsi-nl-dev atftpd[2871]: Serving linu...
von loggenk
17 Jan 2017, 09:50
Forum: Free support
Thema: No PXE boot since Win10 4.0.7.1-2 (SOLVED)
Antworten: 12
Zugriffe: 7900

Re: No PXE boot since Win10 4.0.7.1-2

Hi Scrooge, You're right. Not much info. I thought many users have same problem :-) After opsi-product-updater its not possible to pxe boot in win10-x64 4.0.7.1-2 Other osses can pxe boot. So my idea is that its not the winpe that causes the problem. Correct me if i'm wrong With regards, Kees.......
von loggenk
16 Jan 2017, 13:42
Forum: Free support
Thema: No PXE boot since Win10 4.0.7.1-2 (SOLVED)
Antworten: 12
Zugriffe: 7900

No PXE boot since Win10 4.0.7.1-2 (SOLVED)

Hi All,

After the product-updater i can't pxe boot with Win10.

Windows 7 works without problem. Whats changed?

With regards,

Kees...