Kingskawn
-
Posts
252 -
Joined
-
Last visited
-
Days Won
3
Posts posted by Kingskawn
-
-
test it first in your test lab
from memory...
option 66 is for the wds server name (or ip)
option 67 is for bootfile name
Ok we can close this topic. I already found out what it was. I needed to simply copy the boot file to the PXE server. Something I thought was done and couldn't see in de advertisement status.
-
have you tried configuring options 66 and 67 on the dhcp server ?
No is that a requirement? And if I must, what's the procedure, do you have a guide? I'll test it
EDIT: Just put "\smsboot\x86\pxeboot.com" to the port 67? Not 66? I need to restart DHCP, can't do this in production I suppose otherwise I'll block some people
-
I have one secondary point that cannot deploy images
In the past I had a problem with binlsvc as this wouldn't start the WDS service. To resolve this I have to use the 'initialize' command to configure WDS.
After that WDS/PXE server gave 'PXE-E53 No boot filename received' untill now.
So yesterday I reinstalled it following this:
Everything started directly as it should. (I also had to delete everything inside c:\windows\temp\)
Inside this LAN there is no active VLAN nor DHCP installed on secondary point. Ports 66 and 67 aren't configured for SCCM.
The RemoteInstall folder was empty so I copied this folder from a working secondary point but still no luck.
The pxecontrol.log gives me successful all the time;
Sent 274 bytes to 010.075.011.023:4011~ $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:21:35.055 2010 Romance Daylight Time><thread=3080 (0xC08)>
PXE test request succeeded.~ $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:21:35.274 2010 Romance Daylight Time><thread=3080 (0xC08)>
Successfully performed availability check against local computer.~ $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:21:35.274 2010 Romance Daylight Time><thread=3080 (0xC08)>
Received a registry change notification. $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:26:07.438 2010 Romance Daylight Time><thread=3080 (0xC08)>
------ RegisterForNotification(): Registering again! -------~ $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:26:07.438 2010 Romance Daylight Time><thread=3080 (0xC08)>
Successfully handled registry changes. $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:26:07.453 2010 Romance Daylight Time><thread=3080 (0xC08)>
Received a registry change notification. $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:26:07.453 2010 Romance Daylight Time><thread=3080 (0xC08)>
------ RegisterForNotification(): Registering again! -------~ $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:26:07.453 2010 Romance Daylight Time><thread=3080 (0xC08)>
Successfully handled registry changes. $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:26:07.453 2010 Romance Daylight Time><thread=3080 (0xC08)>
adding address to server list 10.75.11.23 $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:26:35.064 2010 Romance Daylight Time><thread=3080 (0xC08)>
adding address to server list 127.00.00.01 $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:26:35.064 2010 Romance Daylight Time><thread=3080 (0xC08)>
Sending availiability packet to: 10.75.11.23~ $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:26:35.064 2010 Romance Daylight Time><thread=3080 (0xC08)>
Sent 274 bytes to 010.075.011.023:4011~ $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:26:35.064 2010 Romance Daylight Time><thread=3080 (0xC08)>
PXE test request succeeded.~ $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:26:35.283 2010 Romance Daylight Time><thread=3080 (0xC08)>
Successfully performed availability check against local computer.~ $$<SMS_PXE_SERVICE_POINT><ven. mai 07 10:26:35.283 2010 Romance Daylight Time><thread=3080 (0xC08)>
On the client machine when I launch, it gives the correct ip address of the secondary point but says PXE-E53
Also I just saw that the advertised task sequence isn't attached as being advertised to the collection but nevertheless it must give me an abortPXE then?
-
give me more details of this
how is the secondary site setup and what roles are installed on it
The SS is installed on Win2003 R2 x32 with the following roles;
-
- Distribution point (checked "Enable as a standard distribution point", checked "Allow clients to transfer content from" and "allow intranet-only clients")
- Management point (checked "Allow devices to use this management point" and to use the site database)
- PXE Service point (checked "Allow this pxe service point to respond to incoming pxe requests", starts on all network interfaces and certificate goes until 2015)
- Site system (In site system I put the FQDN and checked "Enable this site as a protected site system" with boundary on ip subnet 10.75.8.0)
-
-
Where to begin...
We have 1 primary site with 8 secondary sites. Between them more than 20km so it's over WAN but not through the internet, it's going through the same lan over wan connection.
Bandwidth is more than 10Mbit/s.
Every secondary site has it's own domain name because it's each time another client. All clients do have the same site code that is the one from the primary site server (ours).
They are all using SCCM 2007 SP1 R2 and waiting for SP2 but due to complications with this problem I cannot do it.
We can install perfectly a machine using the task sequences but when I secondary site wants to do the same it doesn't find it's boot package. It finds the secondary site but it cannot boot.
BUT when, in the advertisement, I check the option 'When no local distribution point is available, use a remote distribution point' it will work but it's slower.
So which sites are protected here: all of my secondary sites but not the primary site.
MORE I have a client who has 2 locations and on each location he has a secondary site because he must install machines on both sites. I've put the correct ip subnet as boundary on 1 site and 1 on the other and also protected. Site A has ip subnet 10.75.4.0 (workstations) and is protected but the server is in subnet 10.75.7.0 and isn't in the boundary, could this be the problem or doesn't the ip subnet not be in the boundaries?
I am getting nuts
:angry: -
We are deploying via a command line run on login now, but I would prefer to deploy fully via SCCM so any info would be greatly received.
With this you will be helped I think
-
hi there,
has anyone packaged and deployed via SCCM Trend Micro Office Scan, if so how did you do this, only I'm trying to package this up. i have tried running it as a command line, but when i update the DP it cant copy any info to it as there is none and it says the sequence media is missing.
also when you check the status of the DP it's saying "install pending" for ever.
cheers
Matt
If you still needed, yes I created a package for Trend Micro AV and runs it with success
-
A Software Update always has to be in an Update Package
But if I look in all my updates, I choose 1 update and do 'Deploy Software Updates', it will create a new install for me where I also choose the template and then I've a new line in 'Deployment Management' but nothing in 'Deployment Packages'
How come?
-
When you want RDP 6.0 to be installed on all clients you just have to pick it out of the updates, choose 'Deploy Software Updates' and it will be added into 'Deployment Management' where you can set on what collection it must be distributed.
Am I right?
There mustn't necessary be a 'Deployment Package' to deploy an update, isn't it?
-
Hi Anyweb,
Can you tell us how you can set the pxe boot image to a keyboard layout 'belgian (period)' for example? For SCCM SP2 (WinPE 3.0)
I have already done this for my previous SCCM SP1 R2 (WinPE 2.0) but I can't remember how I did it :angry: :angry: :angry:
-
what about WDS and PXE? Do I also have to stop them when I uninstall WAIK?
-
- I also have to change/update my boot images
- Set the new client install upgrade in each task sequence
- reinstall every sccm client to sp2
What's the difference between full install and upgrade to sp2? I have SCCM SP1 R2 (like most of us)
-
-
I had that problem also in the past on 3 servers which couldn't start the WDS service anymore. Look on google for a command to configure WDS service with one command-line.
Did you installed your SCCM in mixed mode or native? Look out for correct certificates on your SCCM server.
You told that your task sequence is in pending but what are the last lines it shows you?
-
Yes the solution of the port was the thing I said before ;-) I couldn't give you the right link to it at that time but google can still help you
But now you have the question of a pending request. Did you make an advertisement of a task sequence? The capture sequence for instance?
If yes did you check "make this task sequence available to boot media and pxe" ?
To see the log go an look for a log called "SMSPXE.log" on the sccm server. Another source o finformation is technet; My link
-
You also installed WAIK I suppose if you installed the WDS service?
If you filled in all info in SCCM to create a machine then it will sysprep it for you. You can also choose to install a machine with a sysprep file that you create.
As for your problem, so when you advertise a task sequence (OSD) when you start the client computer it boots or it is still looking for an ip address or something else?
Is there a screen that you recognizes?;
-
There are some things you have to check and that maybe are not sccm related.
Check;
- if you have dhcp server active and giving correct ip adresses
- your boundaries in sccm or else you can't pxe at all. they must correspond with your ip ranges in dhcp. there was also something with the ports. wds may have the same port than dhcp, can't remember for sure.
- that you took the correct ethernet drivers for your machine in order that pxe can boot on it
- is the windows deployment service started on your sccm server
These are the first thing I think of
- if you have dhcp server active and giving correct ip adresses
-
And what about all updates that don't have a bulletin ID? Like "Windows Malicious Software Removal Tool - November 2009 (KB890830)", it's from november, so it's relatively new
, but it isn't taken into the updated list -
I found this in the SCCM documentation:
Using an Existing WSUS Server for a Software Update Point
You can use a WSUS server that was active in your environment before installing Configuration Manager 2007, but client computers connecting to the WSUS server will scan for all software updates in the WSUS database. This might result in client computers returning compliance state information for software updates outside of the configured classifications, categories, and languages. Before using an existing WSUS server as an active software update point site system, it is recommended that the software updates metadata is deleted from the WSUS database if possible. The WSUS server will be synchronized with new software updates metadata based on the settings configured for the active software update point.
How do you delete those "software updates metadata" because we had also a working WSUS and coupled our SCCM to it and I never deleted anything but I can see that I don't have all machines in my compliance sheets. I can see there is something that doesn't give the right information.
-
Do I have to delete all the greyed out updates in my update packages or is it automatic?
-
When do you have the problems? Is it when the clients try to install the package or when you are distributing the package to the secundairy site?
It's when the client downloads and installs the package that they can't work anymore because of not enough bandwidth
-
We did a deployment of a package (MS Compatibily Pack 100MB) to a distant location and the bandwidth was full. No business could be done anymore. They had to wait until the deployment was done or I had to stop it in sccm.
So what possibilities do I have? There is BITS in clients and RATE LIMITS in addresses.
I already put the rate limits in addresses from primary site to secondary site at 50%. The problem is that when I want to make a new package for everyone that it takes ages before it gets synchronized to that (problem) secondary site.
Is it better to use BITS in this case such a way that the clients use bandwidth when there is available on his network cable?
I hope it's clear...
-
deployment management contains the actions to deploy the actual packages, think of it as the advertisement,
so, if you want to create a new Deployment Management task, right click on your selected updates in your Search Folders, and choose Deploy Selected Updates, then go through the wizard to create a new Deployment Management task....
don't forget to Refresh the deployment management node...
Today I retried and the symbol next to SP3 in the list went green instead of red. I don't know what changed but the wizard makes a deployment management task and a deployment package.
I can't say what changed
Let's hope that it will deploy on the machines now -
no more clues?
-
That's what I have now;
Where is my deployment managament package?
-
I would kep them separate, easier to manage
see below
Ok I see but now I just made a simple deploy package with just XP sp3 in it and it doesn't make a package in 'Deployment Management' so I cannot target it to a collection.
It only made a deployment package...
PXE-E53 No boot filename received
in Windows Deployment Services (WDS)
Posted
I think it was
For: .\smsboot\x86
abortpxe.com
bootmgr.exe
pxeboot.com
pxeboot.n12
wdsnbp.com
For: .\smsboot\x64
abortpxe.com
bootmgfw.efi
bootmgr.exe
pxeboot.com
pxeboot.n12
wdsnbp.com
And do an update of bootfiles after that