Wds config

Hi all, I have wds configured on my 1242 acces points, I can see on 2 of them, they are configured with "use this AP as wireless domain services" ticked and a priority of 250 and 255 on the other. However the other access points do not have this configured, they only have "enable in swan infrastructure" enabled.
Does this mean, 2 of the ap's are acting as a kind of server for the other ap's, and on the other non wds ap's we only need to enable wds discvery and credentials etc ?

You are correct... here is a link explaining the configuration and setup.
http://www.cisco.com/en/US/docs/wireless/access_point/12.3_7_JA/configuration/guide/s37roamg.html

Similar Messages

  • Join a wireless network vs WDS

    I have the following set up as a WDS:
    Extreme<------>-Express 1<------->Express 2
        main                    relay                      remote
          0'                         40'                            75'
    Apple support a few years back had me set my network up as WDS because of the last unit at 75' away from the base station couldn't connect.
    I'm curious if there have have been any changes over the last two years in the firmware (up to date)  that has improved the distance or likely the
    way extremes and express' handle traffic.  I was thinking of changing to "join" or "extend" as test trying these scenarios:
    Scenario A
         Express 1 = extend
         Express 2 = join
    Scenario B
         Express 1 = join
         Express 2 = join
    Works ok now but when I get a few on the network airplay/airfoil will pause.  I understand the penalty in WDS and would like to give a more traditional
    set up a try.
    I have read several posts on WDS vs standard config but my question is more about the improvements over the past few years.

    Bob,
    Thanks.   iStumbler helped a little.  I noticed that when I switched all AX's to a "join" config I only had one line in istumbler for my network.  When I switched  "Express 1" to extend I had (2) lines in iStumbler and when I was in a WDS config I saw all mac address'.  I think that makes sense.
    When I switched all AX's to "join" I lost connection to the furthest AX (Express 2).
    When I switched the Express 1 to "extend" I was able to see the furthest AX.  I'll leave it in this config for awhile to see how it does. 
    I can't be certain if something has changed in the firmware that makes it work now or if I didn't do the "extend" scenario when I first set it up years ago.  I'm trying to remember if 'extend' was around when I first set it up years ago.

  • Errors in Jdev Trying to Run jsp

    I have a project with 3 files.
    a jsp file that only does ui
    a connection class that attempts to create a connection
    a service class that uses above connection to try to get data.
    I would like to eventually store the password and connection information on an IAS 904 install in
    $ORACLE_HOME/j2ee/wds/config/data-sources.xml
    and
    $ORACLE_HOME/j2ee/wds/config/jazn-data.xml
    So I want to use password obfuscation.
    without using wizards, and directly editing config files, is there a way to set this up? I've tried editing the D:\Program Files\Oracle\jdev904\j2ee\home\config\data-sources.xml
    and
    D:\Program Files\Oracle\jdev904\jdev\system9.0.4.0.1419\oc4j-config\data-sources.xml
    on my local drive, but when I try to run my jsp file, I get the following error:
    oracle.jdeveloper.deploy.DeployException at oracle.jdeveloper.deploy.oc4j.ds.Oc4jDataSourcesNode.syncWithConnectionManager(Oc4jDataSourcesNode.java:68)
    when I run my connection class, I get:
    javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
    Here's my code:
    ublic static Connection getConn() throws Exception
    String JNDINAME="jdbc/pool/OracleCache";
    Context ic = new InitialContext();
    DataSource ds = (DataSource)ic.lookup(JNDINAME);
    Connection conn = ds.getConnection();
    conn.setAutoCommit(false);
    return conn;
    Here is my data-source entry:
    <data-source class="oracle.jdbc.pool.OracleConnectionCacheImpl" name="OracleDS" location="jdbc/pool/OracleCache" connection-driver="oracle.jdbc.driver.OracleDriver" username="scott" password="tiger" url="jdbc:oracle:thin:@host:1521:sid" inactivity-timeout="30" min-connections="3" max-connections="3"><property name="cacheScheme" value="1"/></data-source>
    Do I need to specify anythign else? I don't do any other special configurations. And I'm not very keen on the wizards.
    I'm running 9040.
    Alison

    In jdev there is the Connections tab-page (like run manager or applications); to get your data you can use java code but you also can make a connection to database using wizard :d. It's very simple to get data from tables this way... (there is here a problem: using java code it's possible to gain performace in your application...i'm not so sure).
    Also, you can watch the demos/sample_code from Oracle: (http://www.oracle.com/technology/products/jdev/viewlets/viewlet.html
    and here:
    http://www.oracle.com/technology/sample_code/products/jdev/index.html); those demos are very good.
    bye

  • Too Many Networks Causing Interference

    Hi all,
    I'm running a PB G4 and Toshiba Tecra laptop on a wireless AEBS + AE network using WDS in a first floor apartment. My signal strength throughout the house is usually full bars with the AEBS running at around 45-65 and the AE at 35-45 signal strength depending on what room I'm in.
    Now, sometimes my network just crashes and I receive error messages on the PB and PC telling me that there was an error loggin on to my network or that the connection is incomplete, respectively. My only recourse is to unplug the base station (and AE) and replug it. Usually, this corrects the situation.
    I think this is happening because I detect no less than 5 other networks in my area. There are four units in my building, and the building is part of a row of connected apartment buildings. Adding my AEBS and AE, this makes a total of 7 transmitters in this cramped area! I think this might be creating a wireless blitz.
    FYI, before running my current configuration, I was using a Netgear wireless router with the AE as a client (to stream audio). I switched to the AEBS + AE in WDS config because I thought it would add greater stability and range--which it has. But it seems I might need to "power up" some more in order to fend off the interference from other networks. I realize that this might have bad consequences for those other networks, but something has to be done!
    So, I've been considering boosting my signal by adding an antenna. Is this a solution? I'm also thinking about tweaking the settings for both stations through Admin Utility. Maybe enabling interference robustness on the AEBS, AE, and PB might help?
    Please offer any advice on what you think the problem might be and what might be the best solution.
    Thanks,
    FC

    I think this is happening because I detect no less
    than 5 other networks in my area. There are four
    units in my building, and the building is part of a
    row of connected apartment buildings. Adding my AEBS
    and AE, this makes a total of 7 transmitters in this
    cramped area! I think this might be creating a
    wireless blitz.
    So, I've been considering boosting my signal by
    adding an antenna. Is this a solution?
    I don't think so. You'll increase your signal
    level, and your noise level all together. But
    your signal to noise ratio will reach a limit.
    Exactly like what happens when you turn your radio
    too loud because of the noise of your neighbour's
    one.
    I'm also
    thinking about tweaking the settings for both
    stations through Admin Utility. Maybe enabling
    interference robustness on the AEBS, AE, and PB might
    help?
    Yes.
    But more generally, like every wireless problem of
    interference, you should first analyse it. You
    should use a tool like iStumbler to identify all
    the channels used by your neighbours.
    Once you have identified these channels, and
    their level of signal, you have to choose a channel
    as far as possible of the most powerful ones.
    In an idealistic world, you should choose a channel
    3 channels away of all the channels used by your
    neighbours. (e.g.: if channels 1, 2, 5 & 6 are used,
    you may use channels from 10 to 14, depending on the
    regulations were you're using a wireless network).
    All interference analysis should first go through
    this neighbour's channels hunt.
    If you play randomly with your channels, you're
    wasting your time, you may be disrupting your
    neighbour's networks. And you will have to continue
    this silly danse for a long time all together.

  • Airport extreme/express network setup

    i'm sure this has been covered in general but lan equipment and requirements vary widely (plus most of my wireless experience is w/non-apple routers), so here goes. i have the following hardware
    airport extreme (802.11n) running 7.5.2 (might downgrade to 7.4.x based on comments in this forum) connected to cable modem
    2 airport express (v6.3) connected wirelessly to ap extreme
    1 airport express (v6.3) connected via ethernet (wd powerline) to ap extreme
    what i'd like:
    ap extreme base to be the only SSID & DHCP server on the network.
    the 2 wireless expresses to provide wider coverage in the main house.
    the express connected via ethernet to provide wireless signal/access in the detached guest house (trying to run it wirelessly does not get a strong enough signal, hence the powerline ethernet), but only as an extension to the extreme base.
    when a device (laptop, phone, etc.) connects, it should use the closest / strongest wireless signal, but always think there is only 1 network/connection config. and, when one moves between house and guest house, connected device will auto 'roam'.
    whoever set this up, set the extreme to be running in WDS mode (WDS main). however, it complains that it is the only WDS device on the network (see next ???).
    the 2 wireless expresses are set to 'Participate in WDS' (WDS remote)
    in order to get the ethernet-connected express to work, i had to give it its own SSID and set it to 'Create wireless network'.
    it does work, but there are 2 networks, no roaming, and error message on ap extreme base re:WDS config.
    questions:
    1) what mode should the extreme base use ('Create wireless network' or 'Participate in WDS network')?
    2) what settings (WDS or wireless) for the wireless expresses?
    3) what mode should the ethernet-connected express use ('Create wireless network', 'Participate in WDS network' or 'Join wireless network')?
    4) anything special i need to know to get the roaming to work reliably?
    5) any suggestion (due to missing questions :-)?
    tx for any info. i could try all the permutations & combinations of config (actually, i've already tried a number of them , but tired of running up/downstairs and to/fro resetting devices, so i thought i would ask for help from people with more experience background.
    mack

    Hi, mackiemesser. Welcome to the forums!
    So if I understand correctly, your setup looks like this:
    <hr>
    • Express #1, Express #2, and the Extreme should be set to "Participate in a WDS."
    • The Extreme needs to be told that Expresses #1 and #2 will be WDS Remotes. (You'll have to enter their MAC addresses.)
    • Expresses #1 and #2 need to be told that the Extreme will be their WDS Main. (You'll have to enter its MAC address.)
    • Express #3 should indeed be set to "Create a wireless network" but should use the same SSID and password that your other wireless network uses.
    • All Expresses should be configured to operate in Bridge Mode. In Manual Setup, click "Internet" in the toolbar and choose "Off (Bridge Mode)" from the "Connection Sharing" popup menu.
    • The Extreme should not be in Bridge Mode. It should instead "Share a public IP."
    <hr>
    A few suggestions:
    • Write down the MAC addresses of all your Extremes. This saves a lot of time when you're setting up the WDS.
    • Sometimes after you change the WDS settings for one AirPort on the network, it confuses the other AirPorts in the WDS, and you get network problems until all of the AirPorts agree on WDS information. In this case, if you can't see an AirPort in AirPort Utility, connect that AirPort to the computer via Ethernet. In fact, it might save time to gather all your AirPorts and plug them in next to your computer for the WDS setup process so that you can easily connect via Ethernet if necessary.
    • Using a WDS dramatically decreases your network performance. Every time you add a WDS Remote, you decrease your maximum network speed by 50%. Newer AirPorts support 802.11n and have a feature that allows you to extend your wireless network without as much overhead as a WDS, but all AirPorts in the wireless network that's extended must support 802.11n.

  • Using Airport Express with a Playstation 2?  (Belkin router)

    Hello - I know it seems that this topic has been discussed several times before, but I haven't been able to find a good explanation for how to execute it and would really appreciate any guidance. I'm a mac newbie, too.
    I just purchased a Playstation 2, and would like to use my Airport Express to connect it to my home wireless network. I've used the Airport for other things as well, including to create a wireless network when I travel, and to receive music to play on the stereo. I'm thinking there's GOT to be a way to make this happen.
    I have an Ibook G4, and the rest of the network is a PC setup. (Belkin router.) I can access the Airport Express settings through either the PC or the Mac.
    Any help you can give would really go a long way. Thanks. I'd rather not have to purchase a new bridge if the Airport can do it. What I think I need are step by step instructions to change the settings on the AE to make it work for this application, which I understand is different from 'receiving' music from the router & iTunes.
    Thanks again.

    i use a similar configuration (haven't tried the playstation yet), but the WDS with the Belkin router and Airport Ex works fine.
    for thr belkin:
    - enable wireless bridging
    - turn off security / mac adress filtering first until it works
    config to be done in the Airport Admin utility:
    - turn off security
    - configure the Airport Express as remote station in the WDS config
    - and set in the WDS window: allow wireless clients... and search for the ID of the belkin (should pop up as main airport ID)
    - uncheck: distribute ID adresses in the Network config
    That's how I got it working, but I never got security as WAP working between both stations...the only thing was MAC adress filtering, and hiding the network ID
    Enabling MAC adress filtering worked only after allowing the Ethernet ID of the Airport Ex but NOT the wireless ID, that I specified as: enable only sp. AP to coonect (belkin)
    hope it helps...
    If somewone knows how to get WPA to work between both stations, tell me
    Mac Mini with Airport,, PowerBook G4 400 with Aria Extreme   Mac OS X (10.4.3)   Belkin router F5D-7231-4 and AirPort Express
    Mac Mini with Airport,, PowerBook G4 400 with Aria Extreme   Mac OS X (10.4.3)   Belkin router F5D-7231-4 and AirPort Express

  • GUI v CLI config and WDS question

    Hello-
    I am attempting to deploy a wireless network. I have purchased two 1242Gs and one 1310G WAPs. My goal is to have a WPA V1 protected network utilizing WDS to allow seemless roaming at the location, with a second SSID for guest access that is directed to the gateway. It would be nice if this had a WPA pw also. The 1310 is external to the building where the other two 1242s are. I have attached configuration examples for each. One of my problems is I have to allow support for a legacy Crestron TPMC-10 media controller which is very picky about how its WiFi radio works. Crestron recommends these config lines:
    guest-mode
    mbssid dtim-period 10
    speed basic-1.0 2.0 5.5 6.0 9.0 11.0 12.0 18.0 24.0 36.0 48.0 54.0
    no preamble-short ! CE devices only support Long Preamble
    channel 2462 ! channel 1,6 0r 11 only |
    station-role root ! only one AP may host the SSID intended for TPMC-10
    connectivity.
    beacon dtim-period 3
    no dot11 qos mode ! QOS negatively effects CE connectivity
    no dot11 extension AIRONET ! AIRONET extensions negatively effects CE
    connectivity
    http://support.crestron.com/cgi-bin/crestron.cfg/php/enduser/std_adp.php?p_faqid=3826&p_created=1146514905&p_sid=KHEUTLVi&p_accessibility=0&p_redirect=&p_lva=&p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9MTgsMTgmcF9wcm9kcz0wJnBfY2F0cz0wJnBfcHY9JnBfY3Y9JnBfc2VhcmNoX3R5cGU9YW5zd2Vycy5zZWFyY2hfZm5sJnBfcGFnZT0xJnBfc2VhcmNoX3RleHQ9Q2lzY28gV1BB&p_li=&p_topview=1
    I have read that using the GUI versus the CLI will leave artifacts and other commands not required for operation. Wondering on other's opinions of this and also any recommendations on how to simplify the config files.
    I have attempted to create config files using the CLI examples provided by Crestron but that tends only allow the Crestron to connect and not laptops.
    Any ideas/suggestions are appreciated.

    One wireless router can allow multiple devices to connect to the Internet this is the fundamental behind the Wi-Fi. The following URL will help you:
    http://www.cisco.com/en/US/products/hw/wireless/ps4570/products_configuration_example09186a00801c951f.shtml
    http://www.cisco.com/en/US/products/hw/routers/ps272/products_configuration_guide_chapter09186a008022b1eb.html

  • WDS losing config.

    some of the WDS in my wireless network loose thier client config every once in a while and users cannot authenticate untill i reconfigure. why?

    Ensure that the mobility network-id command is not enabled on the Cisco Access Point (AP) if it serves as the Wireless Domain Services (WDS) device. The mobility network-id command is used for Layer 3 (L3) mobility, and the AP configured as a WDS cannot provide L3 mobility. This command must only be enabled when a Wireless LAN Services Module (WLSM) is used to provide WDS. A WLSM must be the WDS device to properly configure L3 mobility.

  • XP with AirPort Express and WDS ... works brilliant!!! Read how to ...

    I have worked out an interesting setup which uses max. power of AE with my 3Com Router, Dell and Denon AVR-4306.
    It took some hours of testing and finding the right configs, which was a pain in my brain. But now: YEEEHAAA!
    My home setup is:
    - AirPort Express 6.3
    - 3Com OfficeConnect Model 3CRWDR100B-72
    IMPORTANT: IT SUPPORTS WDS!!!
    - Dell Inspiron 9300 with WLAN
    - Epson Stylus Color 740
    - DENON AVR-4306 [Receiver with Ethernet connection]
    Till yesterday I used AE as a client which turns off the ethernet port. And I had a router without WDS support. AND: I had those audio drop outs which made no fun.
    The new configuration at the end is not such complicated.
    AE is connected by WDS to my router, by Toslink and ethernet cable to my receiver. A printer by USB of course.
    Now I am able to:
    - WLAN stream AAC by Dell with AirTunes through AE to my receiver
    - WLAN printing
    - WLAN config of my receiver and internet radio streaming
    - write that posting by WLAN and DSL ... STRIKE!
    AND THE BEST: NO AUDIO DROP OUTS ANYMORE!!!
    The configuration:
    I will not discribe the WLAN setup between my Dell and 3Com in all details because this should be a basic knowledge.
    First I configure router and Dell with WEP. I didn't test WPA with WDS yet. I set the router to my ISP settings to get connection to DSL. The router config by webbrowser is not complex. This is done by the shipped manual. DHCP turned on etc..
    Next step I will setup my DELL for WLAN connection to the router. My router eg. just uses WEP HEX. I can use a ASCII passphrase but this will be converted to HEX. What's now important: I had to use HEX also for DELL WLAN config and AE WITHOUT "$" before the key what's often discribed in the web. Otherwise AE config will give an error message and ASCII will prevent connection by WEP. I set my DELL to IP by DHCP. I use the same ISSD of the router and set WEP. The first setup was done by ethernet cable which is discribed in my manual. After all steps I turned off LAN and am able to connect to WLAN DSL.
    Now the important part:
    I configured the router after config and restart of AE again. The router MUST SUPPORT WDS!!! Otherwise my config will not work. In my 3Com config I turn on WDS and scan for AE when it is set up right. This will grab the right MAC address automatically. But it's also possible to set the AE MAC manually and then:
    I will do a AE reset by holding down the reset button till the yellow light flashes fast. This will set the AE to basic settings. After a while you will recognize the AE's factory name in your WLAN network list on your PC where you also see your router WLAN connection.
    Now drop the router connection by connecting to AE which is unprotected.
    Open the AirPort Admin Utility.
    Choose the factory AE name.
    Open the config.
    Change the password of your AE which is basic "public" to the SAME of your router.
    Choose „AirPort“ and set „Wireless Mode“ to „Create a Wireless Network“.
    Eg. I use for „Network Name“: „DELL9300“ which matches with the SSID of the router.
    Set „Channel“ to „1“ [it seems most robust here].
    Set „Wireless Security“ with WEP. In my case I have to use the router's HEX key.
    On page „Internet“ set „Connect using“ to „AirPort (WDS)“.
    The „MAC Address“ MUST be the MAC address of the WLAN router, BUT THE WLAN ADDRESS ... NOT LAN ADDRESS!!!
    [this was one trap and time killer because I just tried to use the printed MAC address on my routers label which is WRONG because there's a WLAN MAC ADDRESS I found by accident in my router's config overview]
    Activate „Also allow wireless client computers“.
    I use a static IP:
    IP 192.168.1.200
    Subnet 255.255.255.0
    Router 192.168.1.1
    DNS 192.168.1.1
    On page “Network” activate “Distribute IP addresses”.
    On page „WDS“ set to „remote base station“.
    Activate „Allow wireless client computers“.
    You will recognize here that the WLAN MAC address was copied automatically.
    On page "Music" activate AirTunes and define a name. In my case "DENON".
    Save the config to harddrive and then save it to AE.
    AE will restart automatically.
    NOW PRAY! If everything is done right you will reconnect your PC to the router [automatically because AE is dropped or try manually] and after a while the AE lamp shows "green".
    The full power of AE is unlocked and ... actually ... AirTunes still plays without drop outs. GREAT! This could also be router related or WDS works generally better than client mode.
    president

    The 802.11n AirPort Express Base Station (AXn) can be configured in a number of ways when the topic is around extending.
    If you just want to support wired clients, you can configure the AXn as a wireless Ethernet bridge. In this configuration, the AXn would "join" an existing wireless network and share that connection via its Ethernet port.
    The other option is to configure the AXn to extend another AirPort. In this configuration, the AXn would both extend the other AirPort's wireless range, but it would also have its Ethernet port enabled for wired clients.

  • Multiple ethernet connections on a WDS with AirPort Express?

    Going through the AirPort Admin Utility and Airport Setup Assistant, and the various pdf manuals, the only way I can seem to create a WDS is for each device to be a wireless bridge.
    Even setting it up initially as a WDS that connects using AirPort (default config from the setup assistant), then changing it to connect via Ethernet completely broke the bridging and caused much mayhem.
    I'd prefer to set up the new Express device as a wired bridge, as I have a spare ethernet connection on the same subnet. I presume this would lessen the overhead needed by the WDS in general and would speed up the overall performance slightly.
    Does anybody have any clue how to go about this, if it is possible? I bet it's something small and stupid I've overlooked.
    Going back about ten pages in this forum didn't seem to cover this subject, so I apologize if I'm bringing up this subject AGAIN. Oh yeah, and all Airport Express devices involved are on firmware v6.3
      Mac OS X (10.4.8)  

    Disable the distribution of IP Address on the Express setup.
    You don't mention if you are using Airport Express or Extreme for your Main Base. If so then here is the link.
    http://docs.info.apple.com/article.html?artnum=107454
    If you are using a 3rd party Router as your Main Base then you will need to check out one of these 2 links and remember not all 3rd party routers are capable of WDS setup.
    http://discussions.apple.com/thread.jspa?messageID=607414
    and
    http://discussions.apple.com/thread.jspa?messageID=2785566
    Cheers Don

  • Multipmultiple Airport Extreme Base Stations: WDS Or "Extend Wireless Network" To Have Wired -- Wireless Bridge?

    Hello there!
    I've been looking for this info, but have as yet been unable to find it. Here's my scenario:
    I have two Airport Extreme Base Stations (both are dual band) and 3 airport expresses. The main internet connection in my house is in one room, where I have an AEBS as the main wireless router. In another room, I have a bunch of ethernet-only devices. I'd like to use the 2nd AEBS in this room, plug the ethernet devices into it and have the 2nd AEBS act as a wired <--> wireless bridge (connected to the same wireless network as the 1st AEBS). I've attempted this via "extend a wireless network," but the ethernet devices don't get past the AEBS they're plugged into. Should I instead be implementing WDS?
    I mention the airport expresses as I'd like to have airtunes & wireless signal in other areas, but would like to keep the set-up as simple as possible (i.e., not config the AXes for WDS unless it's required).
    Thanks in advance for any help!

    Unlike the 802.11n AirPort Express Base Station (AXn), the 802.11n AirPort Extreme Base Station (AEBSn) cannot be configured as a wireless Ethernet bridge.
    However, there are at least two ways to configure it to provide wired clients access:
    Connect the second AEBSn back to the first by Ethernet; reconfigure the second AEBSn as a bridge and disable its wireless radios, or
    Reconfigure both AEBSns into an extended wireless network. For 802.11n AirPorts, this would be called a dynamic WDS. The AEBSn, connected to the Internet would be the "main" base station and it would only require that you enable the "Allow this network to be extended" option in the AirPort Utility. The extending AEBSn would need to be configured with the option, Wireless Mode = Extend a wireless network, enabled.
    In both configurations, the second AEBSn's Ethernet ports would be enabled for wired clients.

  • Time Capsule WDS trial and error--working now

    *{ I }*
    I consider myself an expert in using Mac computers and Mac wireless systems although I am no hacker and no programmer by any stretch of the imagination (although I did teach myself how to use HyperStacks way back in 1990!). Although Apple overall provides a relative ease of use for computer technology, setting up a WDS network under b or g mode is still not always perfect. In this post, I relay my experiences of using a new Time Capsule to join an existing WDS network in 802.11g mode. It took several trials and errors and there might still be some glitches but for now it seems to be working.
    note: you might want to skip to the last section roman numeral five if you want to skip the "travels with Conal and his Time Capsule" and see what my most helpful hint is.
    *{ II }*
    WDS stands for Wireless Distribution System which is when you use wireless routers to extend the range of your networks using a wireless method rather than linking each router by long cables. In the ideal situation, you would link the routers by cables but in a home situation one may not be able to have unsightly cables hanging everywhere.
    My previous WDS system looked something like this:
    DSL Modem == Extreme ~~ Express1 ~~ Express2 ## laptop
    Key
    == represents wired connection between routers
    ~~ represents wireless connection between routers
    ## represents wireless connection to a wireless device that is not a router (eg., laptop)
    Extreme = Airport Extreme, the previous generation that looked like a saucer (or humourously I have heard called a "boob-style" station.
    Express1 and Express2 = Airport Express, the previous generation that only could broadcast in b or g
    My laptop usually connects to the network from Express2 because that has the strongest signal in my room.
    *{ III }*
    When I received my Time Capsule, I wanted to replace the existing Express2 and make Express2 simply become a wifi client (not a router) so that I can still use it for AirTunes and not to have it broadcast router signals. The reason for this is because Express2 and Time Capsule reside in the same room and aside from the redundancy of network signals, I don't know if having two wireless routers in such close proximity to each other would cause havoc on my network performance. I wanted the network to look like this schematic:
    Extreme ~~ Express1 ~~ Time Capsule
    I unplugged Express 2 and took it to the same location as Express 1 and Extreme 1. Then I plugged in Time Capsule. The idea of putting them in close proximity for set up was so that they could properly configure each other.
    I opened up Airport Utility and it saw all four of my routers. I went through the wizard for Time Capsule selecting the option for it to replace an existing router. When all configurations were automatically set Time Capsule rebooted and in about two minutes or less, Airport Utility tells me there was an error configuring the Time Capsule. I knew immediately then that I had a few long hours ahead of me.
    After that first failure I tried these various ways:
    1. retried the wizard automatic way (never worked for my setup which albeit is not the simplest of network setups is neither the most complicated)
    2. performed a manual configuration whereby I added the Time Capsule Airport ID to Express1 making Time Capsule a remote router of Express1; then I manually added Express1 to TimeCapsule as a router that it should connect to (that didn't work for some reason)
    3. finally I got out the ethernet cable, hard reset Time Capsule, plugged in ethernet cable from laptop to TimeCapsule, and the manually added the Airport ID to Express1 and vice versa.
    Note that I went through trial #2 several times fiddling around with other various WDS configuration etc. Finally what really worked for me was #3. I find that despite that I should be able to configure a new router wirelessly, I was not able to do so with success. I had to do it in a wired ethernet fashion.
    After that was done, all was set. Well, almost because I still had to reconfigure Express2 so that it no longer would work as a router but as a wifi client.
    *{ IV }*
    Now my whole network looks like this
    DSL Modem == Extreme ~~ Express1 ~~ TimeCapsule ## Express2 ## laptop
    Note that Express2 and my laptop are actually both connected wirelessly to TimeCapsule. I am unable to draw it in another way due to the limitations of using linear text to represent parallel items.
    *{ V }*
    So, my advice for those who are having trouble with configuring Time Capsule or other wireless router, sometimes you might want to try plugging in an ethernet cable so that not only is the connection more solid but that pretty much continual contact with the router is available.
    I realise that WDS in 802.11n is configured slightly differently and so perhaps WDS setup has improved but as it stands in 802.11g and 802.11b in the way Apple has implemented it, I would not suggest someone below the level of expert doing it. It can be very baffling, confusing, and irritating. I would never ask my father to try to set up WDS on his own even though there is a wizard for it. I know some people (like Chris Prillo) has had no problems with the wizard, but I have always had problems with the wizard. Not only did I have problems with it when trying to get the Time Capsule to replace an existing router, but when I set up my original WDS network I also couldn't use the wizard to set it up. It kept giving me errors.
    Message was edited by: Conal Ho
    Message was edited by: Conal Ho

    You are over complicating things. I have a Time Capsule (TC), AirPort Extreme (AE) Base Station and AirPort Express (AX) all working flawlessly with WDS.
    Make sure to write down the MAC addresses of the TC, AE, and AX. You will need them to configure WDS.
    Using the AirPort Admin util configure the TC. Turn on WDS and set the TC to be the main.
    Using the AirPort Admin software configure the first AX. Turn on the WDS and set it as a remote client of the TC. You will need the MAC address of the TC.
    Using the AirPort Admin software configure the second AX. Turn on the WDS and set it as a remote client of the TC. You will need the MAC address of the TC.
    You may have to reboot each device after each config change.
    See my blog post on this at http://islandinthenet.com/2008/07/01/airport-everywhere-with-wireless-distributi on-system-wds/
    Message was edited by: Khurt Williams

  • SCCM 2012 R2 - No Response from WDS server

    We upgraded our SCCM 2012 sp1 servers to R2 and have we are now receiving the following error on our remote PXE enabled DP;
    Have performed the usual processes;
    Removed the PXE enabled DP
    Uninstalled the WDS service
    Rebooted server
    Deployed the PXE-DP from the site server (letting the site server also install WDS)
    Checked the WDS service start OK
    Distributed the Boot images to the PXE-DP
    Checked the content status has succeeded
    Checked that the PXE booting clients are looking at the correct server IP
    Checked the smsdpprov.log:
    [AC8][Wed 03/19/2014 15:04:50]:Registry key creation successfull
    [AC8][Wed 03/19/2014 15:04:51]:CSMSDPInstProv::RegisterDPHealthMonTask: Schedule is '00011700001F2000'
    [AC8][Wed 03/19/2014 15:04:51]:1998-01-01T00:00:00Z
    [AC8][Wed 03/19/2014 15:04:54]:A DP health monitoring task has been registered successfully
    [AC8][Wed 03/19/2014 15:04:54]:CSMSDPInstProv::EnableDPUsageStatsGathering entered
    [AC8][Wed 03/19/2014 15:04:59]:Failed to enable IIS logging for DP usage task. Error code: 0x80041013
    [AC8][Wed 03/19/2014 15:05:00]:CcmInstallPXE
    [AC8][Wed 03/19/2014 15:05:00]:RegQueryValueExW failed for Software\Microsoft\SMS\DP, PxeInstalled
    [AC8][Wed 03/19/2014 15:05:00]:RegReadDWord failed; 0x80070002
    [AC8][Wed 03/19/2014 15:05:00]:Running: C:\SMS_DP$\sms\bin\vcredist_x64.exe /q /log "C:\SMS_DP$\sms\bin\vcredist.log"
    [AC8][Wed 03/19/2014 15:05:00]:Waiting for the completion of: C:\SMS_DP$\sms\bin\vcredist_x64.exe /q /log "C:\SMS_DP$\sms\bin\vcredist.log"
    [AC8][Wed 03/19/2014 15:05:10]:Run completed for: C:\SMS_DP$\sms\bin\vcredist_x64.exe /q /log "C:\SMS_DP$\sms\bin\vcredist.log"
    [AC8][Wed 03/19/2014 15:05:10]:Created the DP mutex key for WDS.
    [AC8][Wed 03/19/2014 15:05:10]:Finding Wimgapi.Dll
    [AC8][Wed 03/19/2014 15:05:10]:MsiEnumRelatedProducts failed
    [AC8][Wed 03/19/2014 15:05:10]:FindProduct failed; 0x80070103
    [AC8][Wed 03/19/2014 15:05:10]:MsiEnumRelatedProducts failed
    [AC8][Wed 03/19/2014 15:05:10]:FindProduct failed; 0x80070103
    [AC8][Wed 03/19/2014 15:05:10]:Found C:\Windows\system32\wimgapi.dll
    [AC8][Wed 03/19/2014 15:05:10]:Wimgapi.dll is already installed.
    [AC8][Wed 03/19/2014 15:05:10]:Path to smsdp.dll is 'C:\SMS_DP$\sms\bin\smsdp.dll'
    [AC8][Wed 03/19/2014 15:05:10]:PXE performance counters have been initialized
    [AC8][Wed 03/19/2014 15:05:10]:Machine is running Windows Server. (NTVersion=0X601, ServicePack=1)
    [AC8][Wed 03/19/2014 15:05:10]:WDS is INSTALLED
    [AC8][Wed 03/19/2014 15:05:10]:WDS service is already installed.
    [AC8][Wed 03/19/2014 15:05:10]:Machine is running Windows Server. (NTVersion=0X601, ServicePack=1)
    [AC8][Wed 03/19/2014 15:05:10]:WDS is INSTALLED
    [AC8][Wed 03/19/2014 15:05:10]:Machine is running Windows Server. (NTVersion=0X601, ServicePack=1)
    [AC8][Wed 03/19/2014 15:05:10]:Setting TFTP config key as: System\CurrentControlSet\Services\WDSSERVER\Providers\WDSTFTP
    [AC8][Wed 03/19/2014 15:05:10]:Configuring TFTP read filters
    [AC8][Wed 03/19/2014 15:05:10]:SetupComplete is set to 0
    [AC8][Wed 03/19/2014 15:05:10]:RegQueryValueExW failed for Software\Microsoft\Windows\CurrentVersion\Setup, REMINST
    [AC8][Wed 03/19/2014 15:05:10]:RegReadDWord failed; 0x80070002
    [AC8][Wed 03/19/2014 15:05:10]:REMINST not set in WDS
    [AC8][Wed 03/19/2014 15:05:10]:WDS is NOT Configured
    [AC8][Wed 03/19/2014 15:05:10]:Share (REMINST) does not exist. (NetNameNotFound) (0x00000906)
    [AC8][Wed 03/19/2014 15:05:10]:GetFileSharePath failed; 0x80070906
    [AC8][Wed 03/19/2014 15:05:10]:REMINST share does not exist. Need to create it.
    [AC8][Wed 03/19/2014 15:05:10]:Enumerating drives A through Z for the NTFS drive with the most free space.
    [AC8][Wed 03/19/2014 15:05:10]:Checking Drive: A:\
    [AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
    [AC8][Wed 03/19/2014 15:05:10]:Checking Drive: B:\
    [AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
    [AC8][Wed 03/19/2014 15:05:10]:Checking Drive: C:\
    [AC8][Wed 03/19/2014 15:05:10]:Checking Drive: D:\
    [AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
    [AC8][Wed 03/19/2014 15:05:10]:Checking Drive: E:\
    [AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
    [AC8][Wed 03/19/2014 15:05:10]:Checking Drive: F:\
    [AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
    [AC8][Wed 03/19/2014 15:05:10]:Checking Drive: G:\
    [AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
    [AC8][Wed 03/19/2014 15:05:10]:Checking Drive: H:\
    [AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
    [AC8][Wed 03/19/2014 15:05:10]:Checking Drive: I:\
    [AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
    [AC8][Wed 03/19/2014 15:05:10]:Checking Drive: J:\
    [AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
    [AC8][Wed 03/19/2014 15:05:10]:Checking Drive: K:\
    [AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
    [AC8][Wed 03/19/2014 15:05:10]:Checking Drive: L:\
    [AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
    [AC8][Wed 03/19/2014 15:05:10]:Checking Drive: M:\
    [AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
    [AC8][Wed 03/19/2014 15:05:10]:Checking Drive: N:\
    [AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
    [AC8][Wed 03/19/2014 15:05:10]:Checking Drive: O:\
    [AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
    [AC8][Wed 03/19/2014 15:05:10]:Checking Drive: P:\
    [AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
    [AC8][Wed 03/19/2014 15:05:10]:Checking Drive: Q:\
    [AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
    [AC8][Wed 03/19/2014 15:05:10]:Checking Drive: R:\
    [AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
    [AC8][Wed 03/19/2014 15:05:10]:Checking Drive: S:\
    [AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
    [AC8][Wed 03/19/2014 15:05:10]:Checking Drive: T:\
    [AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
    [AC8][Wed 03/19/2014 15:05:10]:Checking Drive: U:\
    [AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
    [AC8][Wed 03/19/2014 15:05:10]:Checking Drive: V:\
    [AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
    [AC8][Wed 03/19/2014 15:05:10]:Checking Drive: W:\
    [AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
    [AC8][Wed 03/19/2014 15:05:10]:Checking Drive: X:\
    [AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
    [AC8][Wed 03/19/2014 15:05:10]:Checking Drive: Y:\
    [AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
    [AC8][Wed 03/19/2014 15:05:10]:Checking Drive: Z:\
    [AC8][Wed 03/19/2014 15:05:10]:GetVolumeInformation failed: 3
    [AC8][Wed 03/19/2014 15:05:10]:Drive 'C:\' is the best drive for the SMS installation directory.
    [AC8][Wed 03/19/2014 15:05:10]:Creating REMINST share to point to: C:\RemoteInstall
    [AC8][Wed 03/19/2014 15:05:10]:Succesfully created share REMINST
    [AC8][Wed 03/19/2014 15:05:10]:Removing existing PXE related directories
    [AC8][Wed 03/19/2014 15:05:10]:Registering WDS provider: SourceDir: C:\SMS_DP$\sms\bin
    [AC8][Wed 03/19/2014 15:05:10]:Registering WDS provider: ProviderPath: C:\SMS_DP$\sms\bin\smspxe.dll
    [AC8][Wed 03/19/2014 15:05:10]:DoPxeProviderRegister
    [AC8][Wed 03/19/2014 15:05:10]:PxeLoadWdsPxe
    [AC8][Wed 03/19/2014 15:05:10]:Loading wdspxe.dll from C:\Windows\system32\wdspxe.dll
    [AC8][Wed 03/19/2014 15:05:10]:wdspxe.dll is loaded
    [AC8][Wed 03/19/2014 15:05:10]:PxeProviderRegister has suceeded (0x00000000)
    [AC8][Wed 03/19/2014 15:05:10]:Disabling WDS/RIS functionality
    [AC8][Wed 03/19/2014 15:05:10]:PxeProviderUnRegister
    [AC8][Wed 03/19/2014 15:05:10]:
    [AC8][Wed 03/19/2014 15:05:10]:Found privilege otifyPrivilege on service WDSServer
    [AC8][Wed 03/19/2014 15:05:10]:Found privilege SeRestorePrivilege on service WDSServer
    [AC8][Wed 03/19/2014 15:05:10]:Found privilege SeBackupPrivilege on service WDSServer
    [AC8][Wed 03/19/2014 15:05:10]:Found privilege SeSecurityPrivilege on service WDSServer
    [AC8][Wed 03/19/2014 15:05:10]:Privilege SeTakeOwnershipPrivilege NOT found service WDSServer
    [AC8][Wed 03/19/2014 15:05:11]:ChangeServiceConfig2 succeeded for WDSServer. Added privilege SeTakeOwnershipPrivilege
    [AC8][Wed 03/19/2014 15:05:11]:ChangeServiceConfig succeeded for WDSServer. StartType: 0x2
    [AC8][Wed 03/19/2014 15:05:24]:WDSServer status is 4
    [AC8][Wed 03/19/2014 15:05:24]:WDSServer is STARTED
    [AC8][Wed 03/19/2014 15:05:24]:Running: WDSUTIL.exe /Initialize-Server /REMINST:"C:\RemoteInstall"
    [AC8][Wed 03/19/2014 15:05:25]:Waiting for the completion of: WDSUTIL.exe /Initialize-Server /REMINST:"C:\RemoteInstall"
    [AC8][Wed 03/19/2014 15:05:27]:Run completed for: WDSUTIL.exe /Initialize-Server /REMINST:"C:\RemoteInstall"
    [AC8][Wed 03/19/2014 15:05:27]:Machine is running Windows Server. (NTVersion=0X601, ServicePack=1)
    [AC8][Wed 03/19/2014 15:05:27]:No need to configure the firewall
    [AC8][Wed 03/19/2014 15:05:27]:CContentDefinition::GetAllPackagesFromLib failed; 0x80070003
    [AC8][Wed 03/19/2014 15:05:27]:ProcessBootImages failed; 0x80070003
    [AC8][Wed 03/19/2014 15:05:27]:CcmInstallPXE: Deleting the DP mutex key for WDS.
    [AC8][Wed 03/19/2014 15:05:27]:Installed PXE
    [AC8][Wed 03/19/2014 15:05:27]:Registry key creation successfull
    [D48][Wed 03/19/2014 15:08:12]:Registry key creation successfull
    [D48][Wed 03/19/2014 15:08:13]:Registry key creation successfull
    [D48][Wed 03/19/2014 15:08:13]:Registry key creation successfull
    [D48][Wed 03/19/2014 15:08:14]:Registry key creation successfull
    [F20][Wed 03/19/2014 15:08:26]:CcmInstallPXE
    [F20][Wed 03/19/2014 15:08:26]:PXE provider is already installed.
    [F20][Wed 03/19/2014 15:08:26]:Installed PXE
    [F20][Wed 03/19/2014 15:08:26]:CSMSDPInstProv::EnableDPUsageStatsGathering entered
    [F20][Wed 03/19/2014 15:08:26]:1998-01-01T00:00:00
    [F20][Wed 03/19/2014 15:08:27]:A DP usage gathering task has been registered successfully
    [BB8][Wed 03/19/2014 15:10:59]:Content 'ASC0000E.8' for package 'ASC0000E' has been added to content library successfully
    [BB8][Wed 03/19/2014 15:10:59]:Expanding C:\SCCMContentLib\FileLib\24E7\24E71E7B8DBA522A60756D1C2329EE616A364DAB121FFB7A7117D30D4F77A0EC from package ASC0000E
    [BB8][Wed 03/19/2014 15:10:59]:Finding Wimgapi.Dll
    [BB8][Wed 03/19/2014 15:10:59]:MsiEnumRelatedProducts failed
    [BB8][Wed 03/19/2014 15:10:59]:FindProduct failed; 0x80070103
    [BB8][Wed 03/19/2014 15:10:59]:MsiEnumRelatedProducts failed
    [BB8][Wed 03/19/2014 15:10:59]:FindProduct failed; 0x80070103
    [BB8][Wed 03/19/2014 15:10:59]:Found C:\Windows\system32\wimgapi.dll
    [F20][Wed 03/19/2014 15:10:59]:Content 'ASC0000A.7' for package 'ASC0000A' has been added to content library successfully
    [BB8][Wed 03/19/2014 15:10:59]:SetNamedSecurityInfo() failed.
    [BB8][Wed 03/19/2014 15:10:59]:SetObjectOwner() failed. 0x80070003.
    [BB8][Wed 03/19/2014 15:10:59]:SetFileSecurity() failed.
    [BB8][Wed 03/19/2014 15:10:59]:Expanding ASC0000E to C:\RemoteInstall\SMSImages
    [F20][Wed 03/19/2014 15:11:00]:Successfully expanded package ASC0000A to
    \\ASC-DP1.LTCHARITY.ORG.UK\SMSPKGC$\ASC0000A
    [F20][Wed 03/19/2014 15:11:00]:Waiting for another PXE operation thread to finish.
    [F20][Wed 03/19/2014 15:11:05]:Finished waiting.
    [F20][Wed 03/19/2014 15:11:11]:Expanding C:\SCCMContentLib\FileLib\DD54\DD5448253B423537C13072C96F3659FF0D1D51FDA5102BC7A68E4949269A0CA5 from package ASC0000A
    [F20][Wed 03/19/2014 15:11:13]:Finding Wimgapi.Dll
    [F20][Wed 03/19/2014 15:11:13]:MsiEnumRelatedProducts failed
    [F20][Wed 03/19/2014 15:11:13]:FindProduct failed; 0x80070103
    [F20][Wed 03/19/2014 15:11:13]:MsiEnumRelatedProducts failed
    [F20][Wed 03/19/2014 15:11:13]:FindProduct failed; 0x80070103
    [F20][Wed 03/19/2014 15:11:13]:Found C:\Windows\system32\wimgapi.dll
    [F20][Wed 03/19/2014 15:11:19]:SetNamedSecurityInfo() failed.
    [F20][Wed 03/19/2014 15:11:21]:SetObjectOwner() failed. 0x80070002.
    [F20][Wed 03/19/2014 15:11:21]:SetFileSecurity() failed.
    [BB8][Wed 03/19/2014 15:11:44]:Waiting for another PXE operation thread to finish.
    [F20][Wed 03/19/2014 15:11:44]:Expanding ASC0000A to C:\RemoteInstall\SMSImages
    [BB8][Wed 03/19/2014 15:11:49]:Finished waiting.
    [BB8][Wed 03/19/2014 15:11:49]:CcmInstallPXE
    [BB8][Wed 03/19/2014 15:11:49]:PXE provider is already installed.
    [BB8][Wed 03/19/2014 15:11:49]:Installed PXE
    [BB8][Wed 03/19/2014 15:11:49]:CSMSDPInstProv::EnableDPUsageStatsGathering entered
    [BB8][Wed 03/19/2014 15:11:54]:1998-01-01T00:00:00
    [BB8][Wed 03/19/2014 15:11:57]:A DP usage gathering task has been registered successfully
    [BB8][Wed 03/19/2014 15:12:22]:Content 'ASC00003.4' for package 'ASC00003' has been added to content library successfully
    [F20][Wed 03/19/2014 15:13:08]:CcmInstallPXE
    [F20][Wed 03/19/2014 15:13:08]:PXE provider is already installed.
    [F20][Wed 03/19/2014 15:13:08]:Installed PXE
    [E7C][Wed 03/19/2014 15:13:08]:CSMSDPInstProv::EnableDPUsageStatsGathering entered
    [E7C][Wed 03/19/2014 15:13:10]:1998-01-01T00:00:00
    [E7C][Wed 03/19/2014 15:13:10]:A DP usage gathering task has been registered successfully
    [F20][Wed 03/19/2014 15:13:33]:Content 'ASC00027.7' for package 'ASC00027' has been added to content library successfully
    [F20][Wed 03/19/2014 15:13:33]:Expanding C:\SCCMContentLib\FileLib\4681\4681E1F7B35C465F8ADF176C71B2B4CCDA890F2857796DC81EA83B6FC05DBDC3 from package ASC00027
    [F20][Wed 03/19/2014 15:13:33]:Finding Wimgapi.Dll
    [F20][Wed 03/19/2014 15:13:33]:MsiEnumRelatedProducts failed
    [F20][Wed 03/19/2014 15:13:33]:FindProduct failed; 0x80070103
    [F20][Wed 03/19/2014 15:13:33]:MsiEnumRelatedProducts failed
    [F20][Wed 03/19/2014 15:13:33]:FindProduct failed; 0x80070103
    [F20][Wed 03/19/2014 15:13:33]:Found C:\Windows\system32\wimgapi.dll
    [F20][Wed 03/19/2014 15:13:33]:SetNamedSecurityInfo() failed.
    [F20][Wed 03/19/2014 15:13:33]:SetObjectOwner() failed. 0x80070002.
    [F20][Wed 03/19/2014 15:13:33]:SetFileSecurity() failed.
    [F20][Wed 03/19/2014 15:13:33]:Expanding ASC00027 to C:\RemoteInstall\SMSImages
    [AF4][Wed 03/19/2014 15:14:03]:Waiting for another PXE operation thread to finish.
    [AF4][Wed 03/19/2014 15:14:08]:Finished waiting.
    [AF4][Wed 03/19/2014 15:14:08]:CcmInstallPXE
    [AF4][Wed 03/19/2014 15:14:10]:PXE provider is already installed.
    [AF4][Wed 03/19/2014 15:14:10]:Installed PXE
    [AF4][Wed 03/19/2014 15:14:10]:CSMSDPInstProv::EnableDPUsageStatsGathering entered
    [AF4][Wed 03/19/2014 15:14:19]:1998-01-01T00:00:00
    [AF4][Wed 03/19/2014 15:14:22]:A DP usage gathering task has been registered successfully
    [F20][Wed 03/19/2014 15:15:13]:Content 'ASC00002.4' for package 'ASC00002' has been added to content library successfully
    [A9C][Wed 03/19/2014 15:15:56]:CcmInstallPXE
    [A9C][Wed 03/19/2014 15:15:56]:PXE provider is already installed.
    [A9C][Wed 03/19/2014 15:15:56]:Installed PXE
    [A9C][Wed 03/19/2014 15:15:57]:CSMSDPInstProv::EnableDPUsageStatsGathering entered
    [A9C][Wed 03/19/2014 15:15:57]:1998-01-01T00:00:00
    [A9C][Wed 03/19/2014 15:15:58]:A DP usage gathering task has been registered successfully
    ================================================================================
    Checked the SMSPXE.log:
    <![LOG[================= PXE Provider loaded. =====================]LOG]!><time="15:05:22.792+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="smspxe.cpp:137">
    <![LOG[Machine is running Windows Longhorn. (NTVersion=0X601, ServicePack=1)]LOG]!><time="15:05:22.792+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="provsettings.cpp:1112">
    <![LOG[Cannot read the registry value of MACIgnoreListFile (00000000)]LOG]!><time="15:05:22.792+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="provsettings.cpp:353">
    <![LOG[MAC Ignore List Filename in registry is empty]LOG]!><time="15:05:22.792+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="provsettings.cpp:468">
    <![LOG[Begin validation of Certificate [Thumbprint 901708992FC1A759502B2BB7155E20FD7A1385D8] issued to 'dde18d94-b6ea-41d7-8e15-54844518c1b1']LOG]!><time="15:05:22.823+00" date="03-19-2014" component="SMSPXE" context=""
    type="1" thread="2720" file="ccmcert.cpp:1662">
    <![LOG[Completed validation of Certificate [Thumbprint 901708992FC1A759502B2BB7155E20FD7A1385D8] issued to 'dde18d94-b6ea-41d7-8e15-54844518c1b1']LOG]!><time="15:05:22.823+00" date="03-19-2014" component="SMSPXE" context=""
    type="1" thread="2720" file="ccmcert.cpp:1803">
    <![LOG[Initializing PXEPerfObject.]LOG]!><time="15:05:22.823+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="smspxe.cpp:399">
    <![LOG[Could not load logging configuration for component ccmperf. Using default values.]LOG]!><time="15:05:22.823+00" date="03-19-2014" component="SMSPXE" context="" type="2" thread="2720"
    file="stdlogging.cpp:480">
    <![LOG[Unable to open Registry key Software\Microsoft\CCM. Return Code [80070002]. Client HTTPS state is Unknown.]LOG]!><time="15:05:24.414+00" date="03-19-2014" component="SMSPXE" context="" type="1"
    thread="2720" file="ccmutillib.cpp:373">
    <![LOG[Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
    ]LOG]!><time="15:05:24.742+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="libsmsmessaging.cpp:6346">
    <![LOG[PXE::CBootImageInfo::CBootImageInfo: key=]LOG]!><time="15:05:24.742+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="bootimagecache.cpp:60">
    <![LOG[PXE::CBootImageInfo::CBootImageInfo: key=]LOG]!><time="15:05:24.742+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="bootimagecache.cpp:60">
    <![LOG[CContentDefinition::GetAllPackagesFromLib failed; 0x80070003]LOG]!><time="15:05:24.836+00" date="03-19-2014" component="SMSPXE" context="" type="3" thread="2720" file="contentlibrary.cpp:925">
    <![LOG[Begin validation of Certificate [Thumbprint 901708992FC1A759502B2BB7155E20FD7A1385D8] issued to 'dde18d94-b6ea-41d7-8e15-54844518c1b1']LOG]!><time="15:05:24.851+00" date="03-19-2014" component="SMSPXE" context=""
    type="1" thread="2720" file="ccmcert.cpp:1662">
    <![LOG[Completed validation of Certificate [Thumbprint 901708992FC1A759502B2BB7155E20FD7A1385D8] issued to 'dde18d94-b6ea-41d7-8e15-54844518c1b1']LOG]!><time="15:05:24.851+00" date="03-19-2014" component="SMSPXE" context=""
    type="1" thread="2720" file="ccmcert.cpp:1803">
    <![LOG[PXE Provider finished loading.]LOG]!><time="15:05:24.851+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="smspxe.cpp:184">
    <![LOG[Cannot read the registry value of MACIgnoreListFile (800703e5)]LOG]!><time="15:05:29.048+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2700" file="provsettings.cpp:353">
    <![LOG[MAC Ignore List Filename in registry is empty]LOG]!><time="15:05:29.048+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2700" file="provsettings.cpp:468">
    <![LOG[Cannot read the registry value of MACIgnoreListFile (800703e5)]LOG]!><time="15:06:04.490+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="1408" file="provsettings.cpp:353">
    <![LOG[MAC Ignore List Filename in registry is empty]LOG]!><time="15:06:04.490+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="1408" file="provsettings.cpp:468">
    <![LOG[================= PXE Provider shutdown. =====================]LOG]!><time="15:06:39.371+00" date="03-19-2014" component="SMSPXE" context="" type="1" thread="2720" file="smspxe.cpp:223">
    ==============================================================================
    Have we missed something in these logs?
    Can anyone help with this issue please?

    Have you distributed both boot images (x86 and x64) to the PXE-enabled DP?
    Torsten Meringer | http://www.mssccmfaq.de

  • Trying to understand WDS

    Hi all,
    I'm using three AirPort Extremes to form a WDS. For the sake of brevity, I'll abbreviate their function and MAC addresses as:
    Main14
    Relay07
    Remote2C
    All three airports are run in Bridge mode.
    Main14 is at the north end of my home. It is connected by ethernet cable to my DLink router. Main14 is set up as the WDS Main and it has been told that there are two remotes, Relay07 and Remote2C.
    Relay07 is at the south end of my home. It has been told that the main WDS is Main14 and that there is one remote, Remote2C.
    Remote 2C is in an outbuilding south of my home. It has been told that the WDS main is Main14.
    I'm puzzled by two things:
    1) If I pick up my MacBook, fire up Airport Utility and open three config windows, one for each Airport, and click the wireless client option so I can see what clients are being served by each Airport, and beginning at the north end of my home, I start walking south. When I'm next to the main WDS, I see that Main14 is serving the MacBook at a 54 rate. As I walk away from the main toward the relay (and even further south, the remote), the rate drops. I walk past the relay and the rate to the main keeps dropping. I get out to the outbuilding and I see the MacBook transfer from the main to the remote, Remote2C, and the rate goes back up to 54. The MacBook never transfers to the relay. Why not?
    2) Going back to Airport Utility, and again with windows open for each Airport and looking at wireless clients, I can see the three Airports talking to each other. As a typical example,
    Main14 sees client Relay07 at rate 11 and also sees client Remote2C at rate 1.
    Relay07 sees client Main14 at rate 54 and also sees client Remote2C at rate -1.
    Remote2C sees client Main14 at rate 18, but does not see Relay07 at all.
    I don't understand two things here. Why doesn't Remote2C see Relay07 as a client? The relay is much closer to the remote than it is to the main. Second, how are any two units talking to EACH OTHER at different rates? If Main14 is talking to Relay07 at 11, shouldn't Relay07 be talking to Main14 at the same rate? But it isn't; Relay07 is talking to Main14 at 54. This doesn't make sense to me.
    The practical reason I'm asking this, beyond simply trying to understand how the WDS works, is that my wireless connection in the outbuilding is very erratic. One moment I've got a full strength connection, the next I'm utterly disconnected. So I'm guessing that something isn't quite right here. But I don't know what, and I don't really understand how the system is working, so troubleshooting is a bit of a challenge.
    Thanks for any help!
    -brian

    Hi Brian,
    I'm having exactly the same problem, with the slight difference that I'm living in a flat and that the distance between WDS main and WDS relay is 4 meters (with direct line of sight) and the distance between WDS relay and WDS remote is 5 meters... My flat is built around an 'L' shaped corridor with main, relay and remote being each at one point of the 'L'.
    Tried also to scan for used channels and took one of the free ones.
    Can anybody help?
    Thanks,
    Buebeli

  • Windows Deployment Service corrupts \systemroot\system32\config\software in images.

    Hello,
    Recently we have upgraded to Server 2012 R2 to handle our WDS services but some images are not deploying correctly. 
    When checking the event log on the machines that do not deploy correctly, the following error message is discovered: "\systemroot\system32\config\software was corrupted and it has been recovered'
    We can restore the SOFTWARE registry backup from the regback folder and this corrects the problem, but this has to be done after the image is deployed and takes a lot of time.
    The WIM files all deploy fine in all instances of deployment on Server 2008 R2, using DISM directly and ImageX.
    For one image, this only occurs on certain machines.  It has been tested on 3 Z200 with the same hardware setup and the error occurs on 2 consistently and does not occur on the 3rd.
    On another one of the images, this error occurs every time it is deployed using Server 2012 R2 but never when deployed using WDS on Server 2008 R2, DISM or ImageX.
    This occurs whether the deployment is set attended or unattended. The majority of deployments have been tested without using an unattended file to eleminate variables.
    Does anyone have any suggestions? Any ideas would be appreciated.
    Edit:
    We have also exported the WIM file of the image that always "breaks" from WDS 2012 R2 and successfully deployed it every time using 2008R2 WDS DISM and ImageX. 
    We have created separate folders for these problem WIM files so that the RES file only contains the information from the specific WIM that is having problems; this does not fix the problem. 
    Edit 2:
    There is an error in setupact.log but it onlys says that the mentioned registry setting is malformed or corrupt. I tried a web search on this and had results but the majority of the answers were related to errors sysprepping. 
    Starting WDS GUI
    2014-02-12 16:47:07, Warning    [0x0a0180] UI     Failed to change the UI language to en-US.
    2014-02-12 16:47:22, Error      [0x0a0052] UI     Failed to read image data from blackboard[gle=0x00000002]
    2014-02-12 16:47:29, Warning    [0x07008d] DIAG   Win32_Processor : CoInitializeEx returned RPC_E_CHANGED_MODE. Continue. Error code = 0x80010106
    2014-02-12 16:47:31, Warning    [0x070026] DIAG   Win32_Processor : Unable to retrieve Stepping, vtType = 8. Error code = 0x0
    Setting up disk
    2014-02-12 16:47:51, Warning    [0x0606cc] IBS    DeleteFileEx: Unable to clear out attributes on [D:\$WINDOWS.~BT\Sources\Rollback\bootsec.dat]; GLE = 0x2
    2014-02-12 16:47:51, Warning               WDS    CallBack_WdsClient_MulticastCopyFiles: Error transferring files. Falling back to unicast. Error [0x80070002]
    2014-02-12 16:47:51, Warning    [0x0b0095] WDS    CallBack_WdsClient_MulticastCopyFiles: Multicast transfer failed. Error code [0x80070002].
    Active Dir Setup
    2014-02-12 17:11:21, Info       [0x0b0083] WDS    MgLibpOpenLdapConnectionFromDN: DN=
    2014-02-12 17:11:21, Error      [0x0b00c2] WDS    [
    2014-02-12 17:11:21, Info       [0x0b00c2] WDS    <
    2014-02-12 17:11:21, Error      [0x0b00c2] WDS    [
    2014-02-12 17:11:21, Info       [0x0b00c2] WDS    <
    2014-02-12 17:11:21, Error      [0x0b00c2] WDS    [
    2014-02-12 17:11:21, Info       [0x0b007e] WDS    ProcessDomainJoinInformation: MachineName = [(null)], MachineDomain = [(null)]
    2014-02-12 17:11:21, Warning    [0x0b0093] WDS    ProcessDomainJoinInformation: Error resetting machine account. Error [0x80070057].
    2014-02-12 17:11:21, Error      [0x0b00c2] WDS    [
    Set up IBSLIB
    2014-02-12 17:12:39, Info                  IBSLIB Copying files from D:\Windows\Boot\PCAT\en-US to \\?\GLOBALROOT\Device\HarddiskVolume3\Boot\en-US...
    2014-02-12 17:12:39, Info                  IBSLIB SetNamedSecurityInfo failed! Error code = 0x2
    2014-02-12 17:12:39, Info                  IBSLIB Unable to open file \\?\GLOBALROOT\Device\HarddiskVolume3\Boot\en-US\bootmgr.exe.mui for read because the file or path does
    not exist
    2014-02-12 17:12:39, Info                  IBSLIB SetNamedSecurityInfo failed! Error code = 0x2
    2014-02-12 17:12:39, Info                  IBSLIB Unable to open file \\?\GLOBALROOT\Device\HarddiskVolume3\Boot\en-US\memtest.exe.mui for read because the file or
    2014-02-12 17:12:39, Warning               IBSLIB Resource files missing from D:\Windows\Boot\Resources. These files are required for some editions of Windows. If you are servicing older
    versions of Windows, you can ignore this message.
    Sysprep Plug N Play
    2014-02-12 17:14:54, Info                  SYSPRP SPPNP: Removing the devices that are using service mpio ...
    2014-02-12 17:14:54, Info                  SYSPRP SPPNP: The device Root\LEGACY_MPIO\0000 is using the service mpio.
    2014-02-12 17:14:54, Warning               SYSPRP SPPNP: Error 0xE000020B occurred while adding device Root\LEGACY_MPIO\0000 to the device info set.
    2014-02-12 17:14:54, Info                  SYSPRP SPPNP: Finished removing the devices that are using service mpio.
    Sysprep specalize
    2014-02-12 17:18:11, Info       [0x0f008a] SYSPRP RunRegistryDlls:Retrieved section name for this phase as Specialize
    2014-02-12 17:18:11, Warning    [0x0f008f] SYSPRP RunRegistryDlls:Registry key is either empty or malformed: SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\SysPrepExternal\Specialize
    2014-02-12 17:18:11, Info                  IBS    Callback_Specialize: External Providers Specialized Succeeded
    Modify boot entries (Non UFI)
    2014-02-12 17:18:15, Info       [0x0606cc] IBS    Flushing registry to disk...
    2014-02-12 17:18:17, Info       [0x0606cc] IBS    Flush took 1201 ms.
    2014-02-12 17:18:17, Info       [0x06036b] IBS    Callback_SystemRestore: Successfully set System Restore state.
    2014-02-12 17:18:17, Info       [0x0606cc] IBS    GetSystemPartitionNTPath: Found system partition at [\Device\HarddiskVolume1].
    2014-02-12 17:18:17, Warning    [0x0606cc] IBS    GetSystemPartitionPath: Unable to find DOS drive path for system partition [\Device\HarddiskVolume1].
    2014-02-12 17:18:17, Info       [0x0606cc] IBS    GetSystemPartitionNTPath: Found system partition at [\Device\HarddiskVolume1].
    2014-02-12 17:18:17, Warning    [0x0606cc] IBS    GetSystemPartitionPath: Unable to find DOS drive path for system partition [\Device\HarddiskVolume1].
    2014-02-12 17:18:17, Warning               IBSLIB ModifyBootEntriesLegacy: There was an error getting the path to the boot.ini or ntldr. dwRetCode=[0x1F]
    2014-02-12 17:18:17, Warning               IBSLIB ModifyBootEntriesLegacy: We did not successfully complete ModifyBootEntriesLegacy.  This is non-fatal, continuing setup. dwRetCode[0x1F]
    Error in system log:
    Log Name:      System
    Source:        Microsoft-Windows-Kernel-General
    Date:          2/12/2014 5:14:28 PM
    Event ID:      5
    Task Category: None
    Level:         Error
    Keywords:     
    User:          SYSTEM
    Computer:     
    Description:
    {Registry Hive Recovered} Registry hive (file): '\SystemRoot\System32\Config\SOFTWARE' was corrupted and it has been recovered. Some data might have been lost.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Kernel-General" Guid="{}" />
        <EventID>5</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2014-02-13T01:14:28.620907400Z" />
        <EventRecordID>12326</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="364" />
        <Channel>System</Channel>
        <Computer>COMPUTERNAME</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="FinalStatus">0x8000002a</Data>
        <Data Name="ExtraStringLength">36</Data>
        <Data Name="ExtraString">\SystemRoot\System32\Config\SOFTWARE</Data>
      </EventData>
    </Event>
    Sysprep Panther Log:
    2014-02-12 14:39:58, Warning    [0x0f008f] SYSPRP RunRegistryDlls:Registry key is either empty or malformed: SOFTWARE
    \Microsoft\Windows\CurrentVersion\Setup\SysPrepExternal\Cleanup
    2014-02-12 14:39:58, Warning    [0x0f008f] SYSPRP RunRegistryDlls:Registry key is either empty or malformed: SOFTWARE
    \Microsoft\Windows\CurrentVersion\Setup\SysPrepExternal\Generalize
    2014-02-12 14:40:10, Warning                      TapiSysPrep.dll:RetainTapiLocations:RegQueryValueEx() returned 2
    2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service vhdmp was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service VMBusHID was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service Brserid was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service usbcir was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service usbccgp was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service usbhub was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service USBSTOR was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service sffdisk was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service vpcbus was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service umbus was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service swenum was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service rdpbus was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service iScsiPrt was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service CompositeBus was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service circlass was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service ebdrv was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service b06bdrv was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service s3cap was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service 1394ohci was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service usbehci was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service usbohci was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service usbuhci was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service ohci1394 was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service HDAudBus was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service BrUsbMdm was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service BrSerWdm was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service HidBatt was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service MTConfig was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service mouhid was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service kbdhid was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service sfloppy was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service usbprint was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service HidUsb was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service UmPass was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service HidIr was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service HidBth was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service BTHMODEM was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service hcw85cir was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service WacomPen was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service Processor was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service IPMIDRV was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service intelppm was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service AmdK8 was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service AmdPPM was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service AcpiPmi was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service CmBatt was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service sermouse was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service ErrDev was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service WmiAcpi was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service flpydisk was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service fdc was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service Parport was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service pcmcia was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service i8042prt was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.

    We have discovered that this is only happening to target computers with installed
    RAM greater than 4gb. If the machine has greater than 4gb of RAM, the mentioned corruption occurs. If the machine has
    4gb or less, the corruption does not occur. We still have not found a fix for this, (besides removing the excess RAM during imaging and reinstalling after.)  Any ideas/thoughts would be helpful! Thank you in advance.

Maybe you are looking for

  • I would like to find a file manager/ image browser like ACDSee 32

    Coming from the Windows environment (it is where I make my living) I have found the Mac environment to be significantly different and pose a considerable learning curve especially when it comes to file management. I like to be able to view and manage

  • [svn:fx-trunk] 10138: Adding alpha to BitmapFill

    Revision: 10138 Author:   [email protected] Date:     2009-09-10 16:51:52 -0700 (Thu, 10 Sep 2009) Log Message: Adding alpha to BitmapFill http://bugs.adobe.com/jira/browse/SDK-22932 - Border's backgroundAlpha style has no effect when backgroundImage

  • Unable to install downloaded Lightroom pre-sets

    A beginner in relation to Lightroom and unfortunately not very technically savvy. Thus I need your input please. Just downloaded the slit-tone group of pre-sets from Inside Lightroom Website. The instructions on installation seem simple - however, I

  • Changing xml parser from xerces 1 to xerces 2

    Hi Iam installing opencms 6.2 on weblogic 9.1, opencms 6.2 requires xerces 2 whereas the default version for weblogic 9.1 is xerces 1. Please help in changing from xerces1 to xerces 2 in weblogic 9.1 Any help would be graetly appreciated Thanks Chait

  • Keynote not loading since I update OS X Yosemite

    Hello All Recently I purchased a iMac 21.5  Processor 2.7 Intel Core i5, Memory 8 GB, Graphics Intel Iris Pro 1536MB.When I install the update of OS X Yosemite version 10.10.3 my Pages, Keynote and Numbers are not working. It is crashed upon uploadin